Closed
Bug 368451
Opened 19 years ago
Closed 19 years ago
"ASSERTION: Some frame destructors were not called" with :first-letter, :before, counters
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
1.50 KB,
application/xhtml+xml
|
Details |
Reloading this testcase triggers:
###!!! ASSERTION: Some frame destructors were not called: 'mFrameCount == 0', file /Users/admin/trunk/mozilla/layout/base/nsPresShell.cpp, line 645
I don't think this instance of the assertion indicates the presence of an exploitable security hole, but I'd like a fix so I can continue testing for the assertion.
Flags: blocking1.9?
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
At one point while the testcase runs, the CSS quotes "<1>" and "</1>" both appear after the quoted text. Is that behavior correct?
![]() |
||
Comment 3•19 years ago
|
||
> Is that behavior correct?
No. And it happens because we end up with a reframe hint for the first-letter (because its "content" property changed), and the node for the first-letter is the (anonymous) text content. So we try to reframe the anonymous content, and end up putting the frame in a bogus place because we can't compare that sort of thing.
I think the key is really that the content of the first-letter should be the block, not the text. Compare bug 367650.
Blocks: 367650
![]() |
||
Updated•19 years ago
|
![]() |
||
Comment 4•19 years ago
|
||
Fixed by checkin for bug 367650.
Status: NEW → RESOLVED
Closed: 19 years ago
Flags: blocking1.9? → in-testsuite+
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•