When viewing the activity logs for an extension at chrome://extensions/?activity=<extension_id>, certain interactions may cause the page/activities to be from another extension.
Step: navigate to the activity log for any extension, then open a new tab page with an extension override (e.g. Momentum).
a) Search for extension activities
Expected: search should return a subset of activities from the current extension
Actual: search returns activities from another extension
b) Click the "back" arrow to go back to detail view
Expected: the extension for the detail view page should be the same extension as the one on the activity log page
Actual: the detail view page shows a different extension
The cause was the extension id specifically for the activity log page changing too liberally when a chrome.developerPrivate event occurs.
When viewing the activity logs for an extension at chrome://extensions/?activity=<extension_id>, certain interactions may cause the page/activities to be from another extension.
One method to reproduce: navigate to the activity log for any extension, then open a new tab page with an extension override (e.g. Momentum).
a) Search for extension activities
Expected: search should return a subset of activities from the current extension
Actual: search returns activities from another extension
b) Click the "back" arrow to go back to detail view
Expected: the extension for the detail view page should be the same extension as the one on the activity log page
Actual: the detail view page shows a different extension
The cause was the extension id specifically for the activity log page changing too liberally when a chrome.developerPrivate event occurs.
Comment 1 by kelvinjiang@chromium.org
, Today (5 hours ago)