Extension activity logging
Categories
(WebExtensions :: General, enhancement, P1)
Tracking
(firefox70 fixed)
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: aswan, Assigned: mixedpuppy)
References
(Blocks 4 open bugs)
Details
Attachments
(2 files, 2 obsolete files)
Reporter | ||
Comment 1•5 years ago
|
||
I'm about to upload some preliminary (prototype-quality) patches to phabricator associated with this bug.
These patches add tracing of extension api calls, extension events, and content script injection. These patches do not include any UI or other affordance for viewing the logs, but an accompanying extension here can be used:
https://github.com/aswan/firefox-activity-log
Reporter | ||
Comment 2•5 years ago
|
||
Prototype-quality logging for extension api calls, api event dispatches,
and content script injections.
To view extension activity, see:
https://github.com/aswan/firefox-activity-log
Reporter | ||
Comment 3•5 years ago
|
||
This is a quick-and-dirty hack to use the extension logging facility
to log all activity for one or more extensions to disk. It reads a
preference (extensions.logging.ids) at startup, this pref should be a
string that holds a comma separated list of extension ids. For each
listed extension, a log file will be created in the profile directory.
This file will contains JSON blobs for each event, separated by newlines.
This is really a proof-of-concept, the implementation is not optimized
for efficiency and the log file format isn't very usable. But its a
start...
Reporter | ||
Comment 4•5 years ago
|
||
Another very preliminary prototype patch, this annotates fetch() and XHR
references from extensions.
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Comment 6•5 years ago
|
||
Comment on attachment 9056343 [details]
Bug 1542403 Logging extension dom activity prototype
Revision D26426 was moved to bug 1558366. Setting attachment 9056343 [details] to obsolete.
Comment 7•5 years ago
|
||
Comment on attachment 9056261 [details]
Bug 1542403 Add basic persistent logging
Revision D26387 was moved to bug 1558367. Setting attachment 9056261 [details] to obsolete.
Assignee | ||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=0f10826cd1c9c2c6b0afcf4a7fd63cc497f2d310
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 10•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fd509a850479f7762b2031d7cbff19ed2a9aa74a
Comment 11•5 years ago
|
||
Pushed by scaraveo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/847c27f1347c Add extension activity logging facility r=rpl,zombie https://hg.mozilla.org/integration/autoland/rev/ccc2b73ec03c Add privileged activity logging api r=rpl,zombie
Comment 12•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/847c27f1347c
https://hg.mozilla.org/mozilla-central/rev/ccc2b73ec03c
Comment 13•5 years ago
|
||
Hello,
Will this fix require manual validation? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag. Otherwise, could the "qe-verify-" flag be added? Thanks!
Assignee | ||
Updated•5 years ago
|
Description
•