[wpt-sync] Sync PR 62407 - [Extensions] Implement runtime.onEnabled lifecycle event
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox158 fixed)
| Tracking | Status | |
|---|---|---|
| firefox158 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 62407 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/62407
Details from upstream follow.
Justin Lulejian <jlulejian@chromium.org> wrote:
[Extensions] Implement runtime.onEnabled lifecycle event
Currently, extensions have no standard lifecycle event to detect when
they are re-enabled after being disabled by the user or system. While
runtime.onInstalled fires on installation and update and
runtime.onStartup fires on browser profile startup, enabling an
extension does not trigger a dedicated notification to the extension.With this change, extensions can listen to runtime.onEnabled, which
fires whenever an extension transitions from a disabled state to an
enabled state while the browser is running.TAG=agy
CONV=852bdb46-5859-4cdd-9d25-ef2e63da3746Low-Coverage-Reason: COVERAGE_UNDERREPORTED logic executed via extension doesn't seem to get reported.
Fixed: 550432518
Change-Id: I277fd4e05aa4e1e15929b006f6d95347fc510057
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8275812
Auto-Submit: Justin Lulejian \<jlulejian@chromium.org>
Commit-Queue: Justin Lulejian \<jlulejian@chromium.org>
Reviewed-by: Tim \<tjudkins@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1690907}
| Assignee | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Comment 2•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 3•2 months ago
|
||
Test result changes from PR not available.
Comment 5•2 months ago
|
||
| bugherder | ||
Description
•