Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Is there a limit to the number of selectors you can have in a CSS file for Mozilla Firefox to work?

  • 2 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: cor-el

more options

I am writing the CSS code for my website and the CSS is being interpreted correctly by Chrome but is not even being read by Mozilla Firefox. When I use firebug, I can see that the classes appear in the HTML code but are not interpreted in the CSS.

The code for this page was recently added, which puts it on the bottom part of my CSS file. The CSS file has over 2.000 lines. Is it possible that Mozilla Firefox is limiting the number of lines it reads? If so, should I split the code in two or three CSS files (what is the limit per file)?

Thank you!

I am writing the CSS code for my website and the CSS is being interpreted correctly by Chrome but is not even being read by Mozilla Firefox. When I use firebug, I can see that the classes appear in the HTML code but are not interpreted in the CSS. The code for this page was recently added, which puts it on the bottom part of my CSS file. The CSS file has over 2.000 lines. Is it possible that Mozilla Firefox is limiting the number of lines it reads? If so, should I split the code in two or three CSS files (what is the limit per file)? Thank you!

모든 댓글 (2)

more options

I don't think it's an issue of file length, however, as a test you could revert to your previously working file and place all the new CSS in a new file, and see whether that makes any difference.

If you clear the error console and reload the page, do you get any unexpected style warnings? By unexpected, I mean things other than, for example, -webkit-transform is not recognized and is being dropped. Illogical messages can indicate an unnoticed typo.

more options

There is usually an error in the file (e.g. a missing quote) if Firefox doesn't read all rules.

The Error Console (Ctrl+Shift+J) or the Web Console (Ctrl+Shift+K) should show such an error, that possibly had a notification that Firefox reached end of file trying to recover.