-
Notifications
You must be signed in to change notification settings - Fork 86
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Formal review of W3C documents
discussionNeeds further discussionNeeds further discussiontaskRequires work from an individual contributorRequires work from an individual contributorStatus: Open.#1046 In w3c/webextensions;Agenda discussion for public meeting on 2026-07-30
agendaDiscuss in future meetingsDiscuss in future meetingsStatus: Open.#1045 In w3c/webextensions;Add ability to determine if a tab is a new tab page
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timetopic: tabs and windowsTab and window management related issues like split tab, tabgroups, and tab properties, and windows.Tab and window management related issues like split tab, tabgroups, and tab properties, and windows.Status: Open.#1042 In w3c/webextensions;Browser-mediated permission lifecycle for AI agents acting on a user's behalf
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1041 In w3c/webextensions;Review and Feedback requested: Attribution Level 1 2026-06-29 > 2026-07-29
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1040 In w3c/webextensions;Proposal: cross-browser support for cross-origin isolation on extension pages (COOP/COEP manifest keys)
implemented: chromeImplemented in ChromeImplemented in Chromesupportive: firefoxSupportive from FirefoxSupportive from Firefoxsupportive: safariSupportive from SafariSupportive from SafariStatus: Open.#1039 In w3c/webextensions;Browser-hosted OAuth client metadata for WebExtensions
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1038 In w3c/webextensions;The userScripts API should provide a method/option to register overwriting an existing id without us explicitly checking first whether it exists or not
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1036 In w3c/webextensions;Inconsistency: valid characters in extension resource URLs
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1035 In w3c/webextensions;W3C request to transfer the "webextensions" repo to @w3c-cg
adminAdministrative tasks associated with organizing and conducting the group's workAdministrative tasks associated with organizing and conducting the group's workStatus: Open.#1034 In w3c/webextensions;#798 vs #883: How should we empower extensions to add new permissions without overly alarming their current user base?
discussionNeeds further discussionNeeds further discussionfollow-up: chromeNeeds a response from a Chrome representativeNeeds a response from a Chrome representativeneeds-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timeStatus: Open.#1032 In w3c/webextensions;Proposal: Limits on how much data can be set or retrieved at once for extensions with unlimited storage
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timetopic: storageIssues related to persisting data. Topics include browser.storage, web storage, and new APIs.Issues related to persisting data. Topics include browser.storage, web storage, and new APIs.Status: Open.#1028 In w3c/webextensions;