CSS refresh not considering removed properties on live reload

[kutoman]

When I for example have this:

MyStlye {
  color: blue;
}

and remove a specific property:

MyStlye {
}

the Component with MyStyle still keeps the (removed) style property in the simulation

[shannah]

I can't seem to reproduce this. I have added a sample in the SamplesRunner to try to reproduce.

To run the sample, check out the CodenameOne sources from Github, and run the samples target:

$ git clone https://github.com/codenameone/CodenameOne
$ cd CodenameOne
$ ant samples

That will open the Codename One Samples runner, which looks like:

In the "HelloWorldCSS" row, press the "Launch" button to run the sample in the simulator.

Editing the CSS File

With or without the sample running, you can edit the CSS file by going to "More..." > "Edit CSS File"

This will open the CSS file for editing. It will look like:

#Constants {
    includeNativeBool: true; 
}

Label {
    color:red;
}

MyStyle {
    
}

You can change the MyStyle style to:

MyStyle {
    color:blue;
}

And save the file.

Then, with the sample still running, select "More..." > "Refresh CSS"

After a few seconds you should see the text in the sample turn blue.

Now go back to the CSS file, and remove the "color:blue" that you added. Then select "More..." > "Refresh CSS" again. After a few seconds, the text will change back to black.

Please let me know if you get different results, and also please try to modify this sample to reproduce your issue.

[kutoman]

yeah, in that sample it works properly, but is this the same refresh mechanism as the auto refresh during a simulator run? It still doesn't work in my samples.
Could the IDE have any impact on this?

[shannah]

It uses the same auto-refresh mechanism. IDE shouldn't affect this either, as the simulator itself is monitoring the CSS file for changes, and then recompiling as necessary.

[kutoman]

hmm ok, I'll come back if I spot any new hint. Maybe other parts of the css code are somehow blocking the complete refresh since I'm facing the issue in an extensive css.