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)

defect

Tracking

()

People

(Reporter: smaug, Unassigned)

References

Details

Attachments

(1 file)

Attached file testcase
###!!! 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.)
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>.
See Also: → 697791
bz, any thoughts on security rating for this?
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.
Opening this bug up then. Thanks bz!
Group: core-security
Product: Core → Core Graveyard
Product: Core Graveyard → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: