Closed
Bug 1344669
Opened 7 years ago
Closed 7 years ago
Remove Performance::IsEnabled
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla55
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
Details
Attachments
(1 file)
|
5.73 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
Performance API has been enabled by default for quite a while. It's time to remove its preference.
|
Assignee | |
Comment 1•7 years ago
|
||
Assignee: nobody → amarchesini
Attachment #8843908 -
Flags: review?(kyle)
|
||
Updated•7 years ago
|
Attachment #8843908 -
Flags: review?(kyle) → review+
Pushed by amarchesini@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/5c0023fa95e6 Remove Performance::IsEnabled, r=qdot
|
||
Comment 3•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5c0023fa95e6
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
> Performance API has been enabled by default for quite a while. It's time to remove its preference.
That's all, no discussion, no consideration for anything ? I'm going to assume the discussion occurred elsewhere, but since I can't find anything, bear with me :
dom.enable_user_timing disabled the User Timing API, which is one of three API used for fine-grained behavioural tracking and fingerprinting.
Tor Browser disabled it. Have they been made aware of this change ? What did they do to compensate for not being able to disable User Timing API ?
As a Firefox user, I disabled it through about:config. What should I do to compensate the loss ?
|
||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•