Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Why, in Firefox, is only the top/first half of a particular page visible?

  • 4 përgjigje
  • 4 e kanë hasur këtë problem
  • 28 parje
  • Përgjigjja më e re nga DUKEMASKELL

more options

The page in question is http://www.edgewaysbooks.com/shop.html
The whole page is visible in IE and Chrome but, when scrolling down in Firefox, the visible page comes to an end about half-way. In the source code, the whole page is there. I am not the only person who has met the problem.

The page in question is http://www.edgewaysbooks.com/shop.html<br /> The whole page is visible in IE and Chrome but, when scrolling down in Firefox, the visible page comes to an end about half-way. In the source code, the whole page is there. I am not the only person who has met the problem.

Ndryshuar nga cor-el

Zgjidhje e zgjedhur

That is a problem with the HTML5 parser and the above mentioned problem with the unclosed FONT tags. That is causing a lot of deep nesting and the HTML5 parser can't cope with that. In older Firefox versions it was possible to disable the HTML5 parser in such a case as a work around, but that is no longer possible. So that code needs to be cleaned up.


(please do not comment in bug reports)

Lexojeni këtë përgjigje brenda kontekstit 👍 1

Krejt Përgjigjet (4)

more options

Here's what I found. First, it's always good to run a page through the w3c validator to check for errors. Usually rendering problems are caused by a code error. In this case there are lot.

That said, you are right that it works in IE and Chrome. Different browsers deal with errors differently. From looking at the source code and error messages, my guess is that is has something to do with the <font> tags. The first one is opened on line 61 and don't get closed until line 821. In between, they are all nested one inside the other. Ultimately, that may not be the cause but it's hard to tell until things like that are fixed.

more options

Zgjidhja e Zgjedhur

That is a problem with the HTML5 parser and the above mentioned problem with the unclosed FONT tags. That is causing a lot of deep nesting and the HTML5 parser can't cope with that. In older Firefox versions it was possible to disable the HTML5 parser in such a case as a work around, but that is no longer possible. So that code needs to be cleaned up.


(please do not comment in bug reports)

Ndryshuar nga cor-el

more options

Thank you. Will get in touch with the site owners and tell them. When I learn the result, will get back to the forum.

more options

Suggested to site owners they look at your explanation of the problem. They've done so, applied the solution suggested, and ... problem solved! Thanks all round.