Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox ESR 52.4.0 - Single line error in CSS file crashes whole rest of stylesheets - why?

  • 1 răspuns
  • 1 are această problemă
  • 6 vizualizări
  • Ultimul răspuns de cor-el

more options

Hello, a customer works with the latest ESR version of Firefox (52.4.0) and had an issue with his website. The main css file contained an error (something like "background:url(../img url(../img/icon_twitter.png) no-repeat 0 0;") in the middle of the file. While every other browser interpreted the following lines as usual, the Firefox ESR stopped working from this point on, resulting in a partially destroyed layout. (The css file was not merged, compressed or gzipped.) Well, the error was removed and the website is fine now, but is there a reason, why the ESR version doesn' t just ignore errors in single lines? Every other browser behaves like that.

Thanks for your help.

Hello, a customer works with the latest ESR version of Firefox (52.4.0) and had an issue with his website. The main css file contained an error (something like "background:url(../img url(../img/icon_twitter.png) no-repeat 0 0;") in the middle of the file. While every other browser interpreted the following lines as usual, the Firefox ESR stopped working from this point on, resulting in a partially destroyed layout. (The css file was not merged, compressed or gzipped.) Well, the error was removed and the website is fine now, but is there a reason, why the ESR version doesn' t just ignore errors in single lines? Every other browser behaves like that. Thanks for your help.

Toate răspunsurile (1)

more options

Did the Developer Edition work better in this aspect or does it has the same behavior? If there are issues with parenthesis or quotes not getting terminated properly then the behavior in Firefox is unpredictable. You can use this for Troubleshooting purposes or possibly check the number of reported rules and compare this with the expected number. See also the Web Console.