Open
Bug 698224
Opened 14 years ago
Updated 3 years ago
###!!! ASSERTION: Losing track of existing primary frame
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
NEW
People
(Reporter: smaug, Unassigned)
References
Details
Attachments
(1 file)
|
210 bytes,
text/html
|
Details |
###!!! ASSERTION: Losing track of existing primary frame: '!aFrame || !mPrimaryFrame || aFrame == mPrimaryFrame', file ../../dist/include/nsIContent.h, line 890
I'm not yet sure if this case causes security problems.
We really need to fix imagemap handling.
In this case just not-supporting <a> in <map> would be enough.
(Per html4 map can contain a, but html5 has removed that.)
Comment 1•14 years ago
|
||
Ah, so the only reason we don't hit this for <area> is that we make those "display:none !imporant" in html.css, right?
I would be just fine with dropping support for <a> in <map>.
Comment 2•14 years ago
|
||
bz, any thoughts on security rating for this?
Comment 3•14 years ago
|
||
I'm not sure there's an actual security issue here.... We don't lose the frame from the frame tree or anything like that.
Updated•7 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
Product: Core Graveyard → Core
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•