This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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

Why is firefox adding empty lines to the css file in web developer?

  • 1 reply
  • 0 have this problem
  • 9 views
  • Last reply by Waqas Khan

more options

Firefox is adding empty lines to the css file in web developer like so:

  1. videoFiles {
 left: 0;
 z-index: 3;
 width: 250px;
 height: 40px;
 opacity: 0;
 cursor: pointer;

}

  1. image_files {
 height: 40px;
 width: 250px;
 z-index: 3;
 opacity: 0;
 cursor: pointer;

}

.previewVid {

 width: 50%;
 padding: 10px;

}

Those empty lines are not in the css file and so it is reporting the wrong line numbers. So hard to find the correct line in the actual file.

Firefox is adding empty lines to the css file in web developer like so: #videoFiles { left: 0; z-index: 3; width: 250px; height: 40px; opacity: 0; cursor: pointer; } #image_files { height: 40px; width: 250px; z-index: 3; opacity: 0; cursor: pointer; } .previewVid { width: 50%; padding: 10px; } Those empty lines are not in the css file and so it is reporting the wrong line numbers. So hard to find the correct line in the actual file.

All Replies (1)

more options

It sounds like a frustrating issue with Firefox’s Web Developer Tools. The extra empty lines in the CSS are likely being inserted by Firefox’s internal rendering, which can make debugging difficult, especially when trying to match up line numbers with the original CSS file.

One approach you could try is to use a different browser’s developer tools (like Chrome or Edge) to see if they display the CSS without the extra lines. Alternatively, using a text editor with built-in developer tools could also help avoid this issue.

If you need to stick with Firefox, another workaround could be adding comments in your CSS to mark specific sections, which might make it easier to locate the corresponding lines.

Hopefully, a future update to Firefox will resolve this behavior, but in the meantime, these steps might help mitigate the issue.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.