It seems that the pending changes to the parser internals fix this.
Depends on: 515338
I believe this was fixed by the speculative HTML5 parser landing.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Crashtest checked in: http://hg.mozilla.org/mozilla-central/rev/a86c5f1d3fef
You need to log in before you can comment on or make changes to this bug.