"ASSERTION: How could we not have a parent here?" with <caption>, XBL

RESOLVED FIXED

Status

()

Core
Layout: Tables
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Jesse Ruderman, Assigned: bz)

Tracking

(Blocks: 2 bugs, {assertion, testcase})

Trunk
x86
Mac OS X
assertion, testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

674 bytes, application/xhtml+xml
Details
(Reporter)

Description

10 years ago
Created attachment 289990 [details]
testcase

Loading the testcase triggers:

###!!! ASSERTION: How could we not have a parent here?: 'mContent->GetParent()', file /Users/jruderman/trunk/mozilla/layout/tables/nsTableOuterFrame.cpp, line 119
(Reporter)

Updated

10 years ago
Summary: "ASSERTION: How could we not have a parent here?" with <col>, <caption>, XBL → "ASSERTION: How could we not have a parent here?" with <caption>, XBL
(Reporter)

Comment 1

10 years ago
Created attachment 289995 [details]
slightly simpler testcase

Changed the <col> to a <div>.
Attachment #289990 - Attachment is obsolete: true
(Reporter)

Comment 2

10 years ago
See also bug 405186, which involves the same XBL binding and also involves tables.
This is the same issue as bug 405186, really: we have a frame in the frame tree pointing to content that is no longer in the DOM tree.
Depends on: 405186
(Reporter)

Comment 4

10 years ago
I saw this assertion with a build from last night, and I don't see it now that I've updated.

--> FIXED by bug 405186.
Assignee: nobody → bzbarsky
(Reporter)

Comment 5

10 years ago
Should this testcase become an automated regression test too, or is the one in the other bug sufficient?
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
I'd check them both in.
(Reporter)

Updated

10 years ago
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.