Closed Bug 1324683 Opened 8 years ago Closed 8 years ago

stylo: several tests non-fatally assert with "nsStyleSheetService doesn't handle ServoStyleSheets yet"

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: heycam, Assigned: heycam)

References

(Blocks 1 open bug)

Details

###!!! ASSERTION: stylo: nsStyleSheetService doesn't handle ServoStyleSheets yet: 'Error', file /home/worker/workspace/build/src/dom/base/nsDocument.cpp, line 2187

  docshell/base/crashtests/678872-1.html
  dom/base/crashtests/483818-1.html
  js/xpconnect/crashtests/732870.html
  js/xpconnect/crashtests/751995.html
  js/xpconnect/crashtests/752038.html
  js/xpconnect/crashtests/754311.html
  js/xpconnect/crashtests/761831.html
  js/xpconnect/crashtests/786142.html
  js/xpconnect/crashtests/851418.html
  js/xpconnect/crashtests/938297.html
  layout/base/crashtests/121533-1.html
  layout/base/crashtests/143862-1a.html
  layout/base/crashtests/143862-1b.html
  layout/base/crashtests/462392.html
  layout/generic/crashtests/225868-1.html
  parser/htmlparser/tests/crashtests/502869.html
  parser/htmlparser/tests/crashtests/696651-1.html

This one also hits a "Wyciwig Channel  still exists" assertion, but that one is preexisting:

  js/xpconnect/crashtests/753162.html
This is fixed in the latest mozilla-central -> stylo merge.
Status: NEW → RESOLVED
Closed: 8 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
Cameron, this is fixed now right? Should those tests be reenabled?
Flags: needinfo?(cam)
Yes, I'll look at re-enabling those tests.
Assignee: nobody → cam
Flags: needinfo?(cam)
Priority: -- → P3
Looks like these tests got re-enabled when the assertion was downgraded to a warning, in bug 1339341.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.