Closed Bug 1324684 Opened 7 years ago Closed 6 years ago

stylo: layout/generic/crashtests/1271765.html non-fatally asserts with "should no longer be using unconstrained sizes" and "should no longer use available widths"

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: heycam, Unassigned)

References

(Blocks 1 open bug)

Details

###!!! ASSERTION: should no longer be using unconstrained sizes: 'aIEnd != NS_UNCONSTRAINEDSIZE', file /home/worker/workspace/build/src/layout/generic/nsLineLayout.cpp, line 420
###!!! ASSERTION: should no longer use available widths: 'availableISize != NS_UNCONSTRAINEDSIZE', file /home/worker/workspace/build/src/layout/generic/nsInlineFrame.cpp, line 599
###!!! ASSERTION: stylo: We don't support CSS_PSEUDO_ELEMENT_SUPPORTS_USER_ACTION_STATE yet: 'Error', file /home/worker/workspace/build/src/layout/style/ServoStyleSet.cpp, line 191
This is fixed in the latest mozilla-central -> stylo merge.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
This didn't get fixed after all (see bug 1334938); sorry for the noise.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1339341
Summary: stylo: layout/generic/crashtests/1271765.html non-fatally asserts with "should no longer be using unconstrained sizes" and "should no longer use available widths" and "stylo: We don't support CSS_PSEUDO_ELEMENT_SUPPORTS_USER_ACTION_STATE yet" → stylo: layout/generic/crashtests/1271765.html non-fatally asserts with "should no longer be using unconstrained sizes" and "should no longer use available widths"
Priority: -- → P3
Priority: P3 → --
The assertions are no longer fired by this test.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → WORKSFORME
Pushed by ecoal95@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/dc2311553356
Remove stale crashtest annotations. r=me
You need to log in before you can comment on or make changes to this bug.