Open franciscolourenco opened 9 years ago
LiveStyle never commented out rules. It’s pretty complex behaviour to implement. Anyway, I think about it.
Then I was probably referring to when I was using Tincr instead. I don't know how it was implemented but maybe it was saving the modifications chrome does itself when you use the checkboxes:
Would it be simpler to just keep the order of the rules without commenting?
Other case not covered, however minor, is when there are rules already commented the code, and chrome presents them in the inspector as disabled. If you enable them in the inspector, nothing happens in the code.
This is Chrome DevTools feature. Anyway, I agree it’s a big issue so I’ll think about it
I agree with the OP. LiveScript's behavior in this regard is not what I expect or desire. Cheers.
When you temporarily disable a rule using the checkboxes in the web inspector, livestyle deletes the rule and adds it to the end of rules in the css file.
This reveals itself to be a problem when there are order sensitive rules, and your css might get broken just by poking around, and you got no idea why.
Previously, Livestyle would comment rules who got disabled in the web inspector instead of deleting them. It seemed a superior solution because:
The (un)comment behaviour seems a solid metaphor for the web inspector's checkboxes enable/disable action, could we possibly go back to it?