Firebug - why can't I save modified CSS to the server?

    I customized the CSS style of the page in Firebug and thought, why can’t you 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: (there you need to go through the quest in order to download and install this shnyag. Not the point.) - allowing you to save changes in CSS to the server. It works very nicely. I changed the property and immediately, opposite the file containing this style, an icon like “save” appears. Jamnul - and the edit went to the server.

    But there is an unpleasant nuance. Two unpleasant nuances. Firebug does not cling CSS from a file, but from Gecko. Therefore, in the saved result, for obvious reasons, formatting and comments are lost, the structure and order of the rules changes. But, the script that receives the file on the server, this ugliness is very nicely formatted and in the end it turns out even better than it was in the original. :)

    The main problem is that styles that this same Gecko does not understand are lost. As a result, let's say from the entry "-moz-border-radius: 5px; -webkit-border-radius: 5px; border-radius: 5px;" all that remains is "-moz-border-radius: 5px;". the same goes for all IE’s hacks.

    Actually the question is - can this be somehow circumvented, for example, by scattering browser-specific css into different files, or do the listed shortcomings indicate that this is in principle a dead end? Are there any alternatives?

    Also popular now: