Search results

Enhancement: management.ExtensionInfo.disabledReason - add value that indicates the extension has been diabled due to incompatibility or even just client-specific reason

discussionNeeds further discussionNeeds further discussion

enhancementEnhancement or change to an existing featureEnhancement or change to an existing feature

Status: Open.

#941 In w3c/webextensions;

· WoofGrrrr opened on Jan 19, 2026

Provide a way to distinguish prefetch requests from regular navigations in extension APIs

needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first time

needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first time

needs-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first time

Status: Open.

#940 In w3c/webextensions;

· maximtop opened on Jan 16, 2026

Feature request: Support for WEBP as a possible <code>extensionTypes.ImageFormat</code> option

needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first time

needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first time

needs-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first time

Status: Open.

#939 In w3c/webextensions;

· hicallmeal opened on Jan 16, 2026

WebExtensions group website ideation

discussionNeeds further discussionNeeds further discussion

Status: Open.

#938 In w3c/webextensions;

· dotproto opened on Jan 15, 2026

Agenda discussion for public meeting on 2026-01-29

agendaDiscuss in future meetingsDiscuss in future meetings

Status: Open.

#937 In w3c/webextensions;

· Rob--W opened on Jan 15, 2026

Proposal: Limits on lengths of strings passed to WebExtension APIs

supportive: chromeSupportive from ChromeSupportive from Chrome

supportive: firefoxSupportive from FirefoxSupportive from Firefox

supportive: safariSupportive from SafariSupportive from Safari

Status: Open.

#935 In w3c/webextensions;

· bershanskiy opened on Jan 13, 2026

Opt-in Mechanism for Structured Clone Serialization and JSON Fallback Considerations

proposalProposal for a change or new featureProposal for a change or new feature

supportive: chromeSupportive from ChromeSupportive from Chrome

supportive: firefoxSupportive from FirefoxSupportive from Firefox

supportive: safariSupportive from SafariSupportive from Safari

Status: Open.

#931 In w3c/webextensions;

· justinlulejian opened on Dec 22, 2025

Lifecycle event inconsistencies on enable and reload

inconsistencyInconsistent behavior across browsersInconsistent behavior across browsers

needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first time

needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first time

needs-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first time

spec clarificationNeeds clarification when specifiedNeeds clarification when specified

topic: eventsIssues related to the registration, management, and dispatch of WebExtension events.Issues related to the registration, management, and dispatch of WebExtension events.

Status: Open.

#926 In w3c/webextensions;

· carlosjeurissen opened on Dec 7, 2025

Should extension APIs consume user activation?

needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first time

needs-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first time

supportive: chromeSupportive from ChromeSupportive from Chrome

topic: user activationAlso known as a "user gesture"Also known as a "user gesture"

Status: Open.

#920 In w3c/webextensions;

· oliverdunk opened on Nov 27, 2025

Should user gestures be curried between contexts?

implemented: chromeImplemented in ChromeImplemented in Chrome

needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first time

supportive: safariSupportive from SafariSupportive from Safari

topic: user activationAlso known as a "user gesture"Also known as a "user gesture"

Status: Open.

#919 In w3c/webextensions;

· oliverdunk opened on Nov 27, 2025

Grant time-based user activation from extension events that grant a user gesture

supportive: chromeSupportive from ChromeSupportive from Chrome

supportive: firefoxSupportive from FirefoxSupportive from Firefox

supportive: safariSupportive from SafariSupportive from Safari

topic: user activationAlso known as a "user gesture"Also known as a "user gesture"

Status: Open.

#918 In w3c/webextensions;

· oliverdunk opened on Nov 27, 2025

Proposal: Add <code>management.readOnly</code> permission for read-only access to management API

neutral: safariNot opposed or supportive from SafariNot opposed or supportive from Safari

supportive: chromeSupportive from ChromeSupportive from Chrome

supportive: firefoxSupportive from FirefoxSupportive from Firefox

Status: Open.

#917 In w3c/webextensions;

· oliverdunk opened on Nov 27, 2025