Closed
Bug 1522370
Opened 6 years ago
Closed 6 years ago
Lazily report anti-tracking warnings to console
Categories
(Firefox :: Protections UI, enhancement)
Firefox
Protections UI
Tracking
()
RESOLVED
FIXED
Firefox 66
Tracking | Status | |
---|---|---|
firefox66 | --- | fixed |
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
See this profile: http://bit.ly/2FULtlL
We can see that ReportToConsole can be expensive, for example it can incur a call to NS_NewURI, which would cause us to parse a URI from APIs like document.cookie (which can be called quite frequently e.g. from loops inside web pages).
We need to defer these calls to a time when we don't have something better to do, rather than when we have active web page JS code to run!
Assignee | ||
Comment 1•6 years ago
|
||
Pushed by eakhgari@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/efd6f48633c2
Report anti-tracking warnings to console from the idle event queue; r=baku
Comment 3•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 66
Assignee | ||
Comment 4•6 years ago
|
||
Oops, when rebasing this I accidentally pushed the changes for bug 1493361 which I had in my local tree :-(
Pushed by eakhgari@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c418bc9e3fce
Part 2: Remove the changes for bug 1493361 which accidentally crept in here while rebasing
Comment 6•6 years ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•