Closed Bug 390210 Opened 17 years ago Closed 14 years ago

<marquee> fails to close if it contains unclosed <center> tag, scrolls whole page

Categories

(Core :: DOM: HTML Parser, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bugzilla, Unassigned)

References

Details

(Keywords: regression, testcase, Whiteboard: [fixed by the HTML5 parser])

Attachments

(4 files, 1 obsolete file)

In current trunk builds, </marquee> fails to close a scrolling section if it contains an unclosed <center>, see attached testcase: The whole page is "marqueed".

This does *not* happen in branch builds.

To see this in the wild, look at the URL if you feel strong enough.
Regression from bug 369326, it regressed between 2007-02-15 and 2007-02-17.
Blocks: 369326
Attached patch patch (obsolete) — Splinter Review
Not sure whether I should use (kBlock|kSpecial) or kFlowEntity.
I'm not sure in what circumstances I would see the difference.
Attachment #274763 - Flags: review?(mrbkap)
Comment on attachment 274763 [details] [diff] [review]
patch

Martijn, can you add mochitests for <marquee>s as children of random elements? It's hard to know the full extent of one of these changes just via code inspection.

Sorry for the delay in review :-/
Attachment #274763 - Flags: superreview+
Attachment #274763 - Flags: review?(mrbkap)
Attachment #274763 - Flags: review+
Keywords: regression, testcase
No progress here?
Flags: wanted1.9.1?
Flags: wanted1.9.0.x?
Sorry, I still need to make the mochitests that Blake asked in comment 4.
Flags: wanted1.9.0.x?
Ok, sorry for the delay. This is the test that Blake asked for in comment 4.
It can be relatively easily converted into a mochitest.
With the patch applied, nothing changes in the results. This is expected, because it tests something different as the first testcase. I think Blake wanted to be sure that it wouldn't regress some unrelated things.

There are some failure alerts in IE7, which indicates the difference in behavior with Mozilla. It might be interesting to take a look at, but those are only for very special cases, I think.
Ok, now with mochitest.
Without the patch the test fails on one test, with patch it succeeds on all tests.
Attachment #274763 - Attachment is obsolete: true
Attachment #358851 - Flags: review?(mrbkap)
Attachment #358851 - Attachment is patch: true
Attachment #358851 - Attachment mime type: application/octet-stream → text/plain
QA Contact: parser → martijn.martijn
Attachment #358851 - Flags: superreview+
Attachment #358851 - Flags: review?(mrbkap)
Attachment #358851 - Flags: review+
Comment on attachment 358851 [details] [diff] [review]
patch with mochitest

Let's try this on the trunk. I had a momentary flash of panic when thinking about differences in stuff like <marquee><div>, but I doubt that any *real* content has those (famous last words).
(In reply to comment #9)
> (From update of attachment 358851 [details] [diff] [review])
> Let's try this on the trunk. I had a momentary flash of panic when thinking
> about differences in stuff like <marquee><div>, but I doubt that any *real*
> content has those (famous last words).

Yes, well I was wondering about why you weren't asking about that before, but I have done that with the added mochitest in this patch.
I also switched some of the arguments in the first mochitest in the is() function. It doesn't matter for the test itself, but it was used wrongly.
Attachment #359183 - Flags: review?(mrbkap)
Attachment #359183 - Flags: superreview+
Attachment #359183 - Flags: review?(mrbkap)
Attachment #359183 - Flags: review+
Depends on: html5-parsing
Flags: wanted1.9.1?
QA Contact: martijn.martijn → parser
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by the HTML5 parser]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: