Closed Bug 677123 Opened 14 years ago Closed 4 years ago

add "DOMParser" to webworkers

Categories

(Core :: DOM: Core & HTML, defect, P5)

8 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: giorgio.liscio, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110806 Firefox/8.0a1 Build ID: 20110806030740 Steps to reproduce: hi, it is possible to add "DOMParser" inside the worker's scope? thanks
No. The DOM is single-threaded.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:8.0a1) Gecko/20110807 Firefox/8.0a1 (In reply to Ms2ger from comment #1) > No. The DOM is single-threaded. Ok, so this bug should be set as WONTFIX?
I'm talking about a new instance, in fact i don't want to share references as happens with frames (window.parent, contentWindow etc)
The DOM implementation has global state that can't be shared across threads.

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

I haven't seen any realistic spec proposals recently to make core DOM stuff supporting non-main thread.
If that changes, we can always file new bugs.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.