This content has been marked as final.
Show 4 replies
-
1. Re: When using quick edit for compressed CSS, edge code does not jump to the particular class but displays the whole thing. This destroys the whole purpose. Does anyone know a fix or extension for that.
Randy Edmunds Jun 6, 2014 4:32 PM (in response to CodeWreaker)The workaround is to un-minify the CSS while developing.
Thanks,
Randy
-
2. Re: When using quick edit for compressed CSS, edge code does not jump to the particular class but displays the whole thing. This destroys the whole purpose. Does anyone know a fix or extension for that.
CodeWreaker Jun 8, 2014 4:23 AM (in response to Randy Edmunds)Thank you Randy, but some part of the code does not unminify. Some parts of
the CSS is uncoloured. I use the beautify extension to unminify. Thanks
in advance.
-
3. Re: When using quick edit for compressed CSS, edge code does not jump to the particular class but displays the whole thing. This destroys the whole purpose. Does anyone know a fix or extension for that.
Randy Edmunds Jun 8, 2014 9:21 AM (in response to CodeWreaker)I suspect that beautify doesn't touch CSS that it is not aware of (e.g. new properties/syntaxes, vendor-prefixes). See if there's a newer version available.
Which compressed CSS are you using? Most CSS libraries come with both compressed and original stylesheets, so use the original one during development/debugging, and switch to the compressed one for deployment.
Randy
-
4. Re: When using quick edit for compressed CSS, edge code does not jump to the particular class but displays the whole thing. This destroys the whole purpose. Does anyone know a fix or extension for that.
CodeWreaker Jun 20, 2014 6:43 AM (in response to Randy Edmunds)Hello Randy,
I think I found a fix to my problem. An extension that goes directly to the searched keyword in a minifed CSS or JS


