Get rid of dom.workers.enabled pref

RESOLVED FIXED in Firefox 60

Status

()

P2
normal
RESOLVED FIXED
a year ago
9 months ago

People

(Reporter: baku, Assigned: baku)

Tracking

({dev-doc-complete})

58 Branch
mozilla60
dev-doc-complete
Points:
---

Firefox Tracking Flags

(firefox60 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

a year ago
Worker should be always enabled.
Priority: -- → P2
(Assignee)

Comment 1

a year ago
Created attachment 8947480 [details] [diff] [review]
pref.patch
Attachment #8947480 - Flags: review?(bkelly)
Attachment #8947480 - Flags: review?(bkelly) → review+

Comment 3

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/4191749c2609
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox60: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Keywords: dev-doc-needed
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 5

a year ago
I vote against this proposal.

Comment 6

11 months 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.
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

9 months 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.
You need to log in before you can comment on or make changes to this bug.