Closed
Bug 1434934
Opened 7 years ago
Closed 7 years ago
Get rid of dom.workers.enabled pref
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Tracking
()
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
9.76 KB,
patch
|
bkelly
:
review+
|
Details | Diff | Splinter Review |
Worker should be always enabled.
Updated•7 years ago
|
Priority: -- → P2
Updated•7 years ago
|
Attachment #8947480 -
Flags: review?(bkelly) → review+
Pushed by amarchesini@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/4191749c2609 Remove dom.workers.enabled pref, r=bkelly
Comment 3•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4191749c2609
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Updated•7 years ago
|
Keywords: dev-doc-needed
Comment 4•7 years ago
|
||
Probably not *really* worth mentioning, but I've added a small note anyway: https://developer.mozilla.org/en-US/Firefox/Releases/60#DOM
Keywords: dev-doc-needed → dev-doc-complete
Comment 6•7 years ago
|
||
Can someone please explain the REASONS WHY "Worker should be always enabled" as per comment 1 . Is it some technical reason / code simplification, or some arbitrary decision that workers are becoming more mainstream and the wider public is not allowed to "break" things? Being able to disable workers is a valid privacy mechanism.
Comment 7•7 years ago
|
||
Disabling workers is not a privacy enhancing change. I don't know why people have that impression. Dedicated and shared workers only live as long as there is a window opened to the given origin. Service workers can run in the background if you grant push notifications, etc, but we still have a pref to disable service workers and we disable them depending on various privacy options set by the user. Its not feasible to disable workers completely in firefox because the browser itself depends on them.
Comment 8•6 years ago
|
||
> Disabling workers is not a privacy enhancing change. I don't know why people have that impression.
Worker SAB was the initial timing intrinsic used to run Spectre in browsers, and some people may be wary of additional timing intrinsics that have yet to be discovered or disclosed. I don't feel strongly about this issue, although I disagree with your statement about privacy. Disabling workers decreases attack surface, increasing security and, by extension, privacy.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•