Closed Bug 460323 Opened 13 years ago Closed 13 years ago
[FIX]"ASSERTION: Bad loading table" involving get
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
If the already-loaded sheet is modified, we need to fall back on looking at loading sheets, not just creating a new sheet.
Summary: "ASSERTION: Bad loading table" involving get.live.com → [FIX]"ASSERTION: Bad loading table" involving get.live.com
Pushed changeset 457619abbaa5. Jesse, any idea how to sanely turn this into a crashtest? The hard part is knowing when to stop the test.... :(
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
If you use setTimeout at the end of doIt, are you guaranteed that the stylesheets all load before the timeout fires, thanks to using data: URLs? Or can you use the DOM styleSheet API to tell whether the stylesheets have all loaded, and even test that the second and third stylesheets weren't modified by the call to change the first one?
No guarantees on data:. And DOM stylesheet doesn't provide "has this sheet loaded?" info, really. I suspect the test will have to wait on bug 185236.
Depends on: 185236
You can use the DOM Stylesheet API to see whether all the rules are there, but I guess that's not quite the same thing as knowing whether it has finished loading.
Flags: in-testsuite? → in-testsuite+
Nah, this was fixed for like Firefox 3.5 or something. That last checkin was just a test.
Target Milestone: mozilla10 → mozilla1.9.1
You need to log in before you can comment on or make changes to this bug.