| Summary: | browser.commands: Empty browser action reference causes conflicts | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Carlos J. <carlosj-webkit-bugzilla> |
| Component: | WebKit Extensions | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ap, timothy |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Previously reported as: https://feedbackassistant.apple.com/feedback/9633205 https://developer.apple.com/forums/thread/690181 This was fixed in Safari (not in WebKit) in iOS 16. Please reopen if this still reproduces for you. rdar://83232949 Thanks! Good to know! |
To provide users the ability for a keyboard shortcut to open extensions, you can define this in manifest: ``` "commands": { "_execute_browser_action": { "description": "Open extension popup" } }, ``` This doesn't set a keyboard shortcut yet allows the user to assign one. However, in iOS safari, when two extensions offer this functionality, the browser warns about it. See screenshot. Sample extension can be found here: https://github.com/carlosjeurissen/webext-tech-demo-extensions/tree/main/issues/safari-9633205-duplicate-empty-command-conflict