Firebug - why can't I save the modified CSS to the server?
Customized CSS style page in Firebug and thought, why can not save these changes directly to the server? It would be very nice - you can save a bunch of time. It turns out you can.
There is a FireFile addon: https://addons.mozilla.org/de/firefox/addon/52365/ (there you need to complete a quest in order to download and install this shnyaga. Not the essence.) - allowing you to save changes to the CSS on the server. It works very nicely. I changed the property and immediately, in front of the file containing this style, an icon like “save” appears. Zamnul - and editing went to the server.
But there is an unpleasant nuance. Two unpleasant nuances. Firebug does not catch CSS from a file, but from Gecko. Therefore, in understandable result, for obvious reasons, formatting and comments are lost, the structure and order of rules changes. But, the script accepting the file on the server, this disgrace very nicely formats and as a result it turns out even better than it was in the original. :)
The main problem is that they lose styles that this very Gecko does not understand. As a result, say, from the record "-moz-border-radius: 5px; -webkit-border-radius: 5px; border-radius: 5px;" it only remains "-moz-border-radius: 5px;". The same applies to all IE'shnyh hacks.
')
Actually the question is - can this be somehow circumvented, say, by scrolling through browser-specific css across different files, or the listed disadvantages suggest that this is in principle a dead-end path? Are there any alternatives?
There is a FireFile addon: https://addons.mozilla.org/de/firefox/addon/52365/ (there you need to complete a quest in order to download and install this shnyaga. Not the essence.) - allowing you to save changes to the CSS on the server. It works very nicely. I changed the property and immediately, in front of the file containing this style, an icon like “save” appears. Zamnul - and editing went to the server.
But there is an unpleasant nuance. Two unpleasant nuances. Firebug does not catch CSS from a file, but from Gecko. Therefore, in understandable result, for obvious reasons, formatting and comments are lost, the structure and order of rules changes. But, the script accepting the file on the server, this disgrace very nicely formats and as a result it turns out even better than it was in the original. :)
The main problem is that they lose styles that this very Gecko does not understand. As a result, say, from the record "-moz-border-radius: 5px; -webkit-border-radius: 5px; border-radius: 5px;" it only remains "-moz-border-radius: 5px;". The same applies to all IE'shnyh hacks.
')
Actually the question is - can this be somehow circumvented, say, by scrolling through browser-specific css across different files, or the listed disadvantages suggest that this is in principle a dead-end path? Are there any alternatives?
Source: https://habr.com/ru/post/93511/
All Articles