Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

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

  • 1 odgovor
  • 0 ima to težavo
  • 9 ogledov
  • Zadnji odgovor od 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.

Vsi odgovori (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.

Koristno?

Vprašajte

Če želite objaviti odgovor, se morate prijaviti v svoj ​​račun. Če računa še nimate, zastavite novo vprašanje.