Closed
Bug 20399
Opened 25 years ago
Closed 25 years ago
[bugday] MouseOver causing uncalled-for page reflow and growth.
Categories
(Core :: DOM: HTML Parser, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: jelwell, Assigned: rickg)
References
()
Details
Attachments
(1 file)
|
121 bytes,
text/html
|
Details |
Load the page in Build 1999112908 on NT or 199913008 Linux 2.2.13.
Now MouseOver a date, any date.
Watch the page grow...
I think it grows 3 tables per mouseover, but the mouseover appears to be a
continuous effect, so it can grow pretty fast.
|
||
Comment 1•25 years ago
|
||
|
|
||
Comment 2•25 years ago
|
||
Very odd indeed, the source of the reduced testcase is:
<html>
<body>
<a name="unterminated_anchor" href="bogus_href">
foo
<!---->
<hr>
</body>
</html>
There seems to be some interaction between the unterminated <a>nchor and
surrounding tags. In this testcase, you can avoid the failure by removing the
(blank!) comment, go figure. Also of note, if you take the bogus href=""
attribute out of the <a>nchor tag, you need to click on the word foo to see the
failure.
This is clearly NOT related to the javascript engine
(see http://www.mozilla.org/js/tests/library.html to see what the Javascript
Component actually covers), and I really havn't got a clue who it might belong
to, I'll reassign it after asking around.
|
|
||
Comment 3•25 years ago
|
||
Just to confirm what the testcase is supposed to show:
Expected:
Moving your mouse over the "foo" link displays "bogus_href" in the status line.
Actual:
Moving your mouse over the "foo" link causes new <hr>s to be written to the
document. (!)
|
|
||
Updated•25 years ago
|
Component: Javascript Engine → Parser
|
|
||
Comment 4•25 years ago
|
||
Assigned to parser because it probably should have caught the bad html. (I
could be wrong) I imagine layout has something to do with this as well.
|
|
||
Updated•25 years ago
|
QA Contact: rginda → janc
|
|
||
Comment 5•25 years ago
|
||
qa contact to janc, why didn't the assigned-to change?
|
||
Comment 6•25 years ago
|
||
this happens on abcnews.com as well. wow.
|
|
||
Updated•25 years ago
|
Assignee: mccabe → rickg
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I have no idea why this would be described as a parser bug. The content model is
well formed. In fact, I can't even reproduce the problem cited by the bug.
|
||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
|
|
||
Comment 8•25 years ago
|
||
works for me too.
You need to log in
before you can comment on or make changes to this bug.
Description
•