X
點擊此處開啟此網站的行動版。

技術支援討論區

How come this url presents itslf correctly in Chrome, but wrongly in firefox?

已張貼

A page written in classic ASP (by me) presents itself perfectly in Chrome, but not in Firefox. How can that be?

http://www.nadars.org.uk/g3rvm_Contests.asp

A page written in classic ASP (by me) presents itself perfectly in Chrome, but not in Firefox. How can that be? http://www.nadars.org.uk/g3rvm_Contests.asp

額外的系統細節

已安裝的外掛程式

  • Shockwave Flash 32.0 r0

應用程式

  • User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:65.0) Gecko/20100101 Firefox/65.0

更多資訊

WestEnd 60 個解決方法 5387 個答案

Looks the same to me on both Browser. So what does your screenshot look like for each?

Looks the same to me on both Browser. So what does your screenshot look like for each?

由 WestEnd 於 修改

FredMcD
  • Top 10 Contributor
4259 個解決方法 59636 個答案

Hello,

In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see How do I create a screenshot of my problem?

Once you've done this, attach the saved screenshot file to your forum post by clicking the Browse... button below the Post your reply box. This will help us to visualize the problem.

Thank you!

Hello, In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see [[How do I create a screenshot of my problem?]] Once you've done this, attach the saved screenshot file to your forum post by clicking the '''Browse...''' button below the ''Post your reply'' box. This will help us to visualize the problem. Thank you!
cor-el
  • Top 10 Contributor
  • Moderator
17538 個解決方法 158577 個答案

The Inspector shows that there are a lot of font tags nested on that page.

Firefox gives up after a specific number of nesting levels (I think 200) and no longer renders the page properly. Font tags need to be closed properly (</font>), but these tags are missing and for every item a new font tag is opened. You can see in the second screenshot that Firefox generates all these closing tags at the end of the DIV container.

The Inspector shows that there are a lot of font tags nested on that page. *https://developer.mozilla.org/en-US/Tools/Page_Inspector Firefox gives up after a specific number of nesting levels (I think 200) and no longer renders the page properly. Font tags need to be closed properly (</font>), but these tags are missing and for every item a new font tag is opened. You can see in the second screenshot that Firefox generates all these closing tags at the end of the DIV container.

由 cor-el 於 修改