Closed
Bug 1887817
Opened 2 years ago
Closed 1 year ago
Document.parseHTMLUnsafe throw error: NS_ERROR_UNEXPECTED
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
FIXED
128 Branch
People
(Reporter: 94529818, Assigned: avandolder)
References
Details
Attachments
(2 files)
Steps to reproduce:
Execute Document.parseHTMLUnsafe('<p></p>') .
Actual results:
Throw error:
Uncaught NS_ERROR_UNEXPECTED
Expected results:
Execute successfully.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
| Assignee | ||
Updated•2 years ago
|
Severity: -- → S3
| Assignee | ||
Updated•2 years ago
|
Assignee: nobody → avandolder
| Assignee | ||
Updated•2 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
| Assignee | ||
Comment 3•1 year ago
|
||
It doesn't throw the error any more in version 126.
But returns a "Restricted Object".
Pushed by avandolder@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/35521d03c3c7
Create document for parseHTMLUnsafe within the correct docgroup. r=dom-core,jjaschke
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-128b-p2]
Issue is reproducible on a 2024-03-26 Nightly build on Windows 10.
Verified as fixed on Firefox 128.0b3 and Firefox Nightly 129.0a1 on Windows 10, Ubuntu 22, macOS 14.
You need to log in
before you can comment on or make changes to this bug.
Description
•