multiple unclosed center tags result in page rendering failing

RESOLVED INCOMPLETE

Status

()

--
minor
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: tails_naf, Unassigned)

Tracking

2.0 Branch
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-10-01])

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

A webpage with multiple <center> tags followed by other html will eventually fail rendering.
In a locally generated webpage - about 2 megs of tables (200 or so tables) where each table is prefixed by <center>, but the <center> tag is not closed, will eventually fail to render - the tables towards the end will fail to be rendered.

A possible work-around would be to automatically close the <center> tag on encountering another <center>.

Reproducible: Always

Steps to Reproduce:
1. Generate a webpage with a large number of individaul tables (any number of rows / cols)
2. Before each <table> instert a <center> tag. Do not close the tag.
3. Display in FF
Actual Results:  
Last X number of tables will be corrupt. Viewing the source in FF (view selection source) will show the DOM has incorrectly intterpret the HTML

Expected Results:  
all tables should be rendered correctly. 

While this is not 'wonderful' html - this issue does not show in other browsers.
I imagine the rate of occurance is low, but it still shows up poorly. 

No errors are thrown by FF when this occurs. Tracking down the cause of the issue to the multiple <center> tags took quite a lot of debug (trial and error),
Reporter, are you still seeing this issue with Firefox 3.6.9 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-10-01]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.