Closed
Bug 1232875
Opened 9 years ago
Closed 2 years ago
"Assertion failure: !parent->GetPrevInFlow() (Col group should always be in a first-in-flow table frame)"
Categories
(Core :: Layout: Tables, defect)
Core
Layout: Tables
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox46 | --- | affected |
People
(Reporter: jruderman, Assigned: dholbert)
References
Details
(Keywords: assertion, testcase)
Attachments
(3 files)
###!!! ASSERTION: Shouldn't be incomplete if availableBSize is UNCONSTRAINED.: 'aReflowState.AvailableBSize() != NS_UNCONSTRAINEDSIZE', file layout/generic/nsBlockFrame.cpp, line 1575
Assertion failure: !parent->GetPrevInFlow() (Col group should always be in a first-in-flow table frame)
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Assertion failure: !parent->GetPrevInFlow() (Col group should always be in a first-in-flow table frame), at layout/tables/nsTableColGroupFrame.h:42
Comment 3•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: critical → --
Assignee | ||
Comment 4•2 years ago
|
||
No assertions anymore. --> WORKSFORME, and I'll add a crashtest.
Severity: -- → S3
Status: NEW → RESOLVED
Closed: 2 years ago
Component: Layout → Layout: Tables
Flags: needinfo?(dholbert)
Resolution: --- → WORKSFORME
Assignee | ||
Comment 5•10 months ago
|
||
Updated•10 months ago
|
Assignee: nobody → dholbert
Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fd1e72bb8065
Add wpt crashtest for this (fixed) bug. r=layout-reviewers,emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/44392 for changes under testing/web-platform/tests
Comment 8•10 months ago
|
||
bugherder |
Updated•10 months ago
|
Flags: in-testsuite+
Upstream PR merged by moz-wptsync-bot
Assignee | ||
Updated•10 months ago
|
Flags: needinfo?(dholbert)
You need to log in
before you can comment on or make changes to this bug.
Description
•