Closed Bug 1177968 Opened 9 years ago Closed 1 year ago

remove dom.caches.enabled pref

Categories

(Core :: Storage: Cache API, task, P5)

task

Tracking

()

RESOLVED FIXED
117 Branch
Tracking Status
firefox117 --- fixed

People

(Reporter: bkelly, Assigned: gregp)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

After Caches API has been in release for a cycle or two we should remove dom.caches.enabled pref completely.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Component: DOM: Core & HTML → Storage: Cache API
No longer blocks: 1110136

Here's a good reason NOT to remove it:
https://github.com/Tampermonkey/tampermonkey/issues/773

(In reply to Alex from comment #1)

Here's a good reason NOT to remove it:
https://github.com/Tampermonkey/tampermonkey/issues/773

Hi Alex, if you suspect a bug in Firefox itself causing this issue, could you please file a new bug with clear STR for this specific problem here in bugzilla? Thank you!

Flags: needinfo?(bugzilla)

(In reply to Jens Stutte [:jstutte] from comment #2)

Hi Alex, if you suspect a bug in Firefox itself causing this issue, could you please file a new bug with clear STR for this specific problem here in bugzilla? Thank you!

Hello Jens,

I opened bug https://bugzilla.mozilla.org/show_bug.cgi?id=1643405 based on reports on TamperMonkey github.

That said, given my experience with the bug system (searching for solutions for problems I encountered with FF only to find out that those are bugs that have been reported seven years ago, for example: #866522 and #850906) I respectfully request that the existing workaround not be removed until the underlying issue is addressed.

Thank you,
Alex.

Flags: needinfo?(bugzilla)
See Also: → 1643405

Hey Andrew, does this also fall into the emergency pref area? https://bugzilla.mozilla.org/show_bug.cgi?id=1488583#c0 removed the pref for IndexedDB arguing that cookies and site data permissions are sufficient, but it seems it's been replaced by ETP.

Flags: needinfo?(bugmail)

I think we can probably remove the cache API preference as the risk profile is low (and resembles that of IndexedDB's rationale in bug 1488583 although this pref hasn't caused crashes that I know of). I think we'll want to continue to have the service workers enabling pref, though, as its moving parts do have a higher risk profile (in the abstract). Thanks for proactively looking at this!

Flags: needinfo?(bugmail)

Thanks! I just found this while looking at longstanding issues.

Edit: This one is simpler as it actually hides the relevant attributes/interfaces while the IndexedDB one did not.

Blocks: old-prefs
Type: defect → task
Assignee: nobody → gp3033
Status: NEW → ASSIGNED
Pushed by gp3033@protonmail.com: https://hg.mozilla.org/integration/autoland/rev/9db33f9464a6 Remove dom.caches.enabled pref r=webidl,devtools-reviewers,saschanaz,asuth
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: