Skip to content

Proposal: agree on a unified sidebar_action API for mv3 #128

@carlosjeurissen

Description

@carlosjeurissen

Since sidebar_action is not implemented in Chromium we have the opportunity to still define what it should look like in mv3.

In mv2, this has been implemented by Mozilla Firefox, Opera and Naver Whale. Yet they are different across browsers. See:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/sidebar_action
https://developers.whale.naver.com/api/extensions/sidebarAction/
https://dev.opera.com/extensions/sidebar-action-api/

One of the differences is the support of sidebar_action next to another action in Firefox and Opera, but not in Naver Whale. Another is the lack of open_at_install in Opera. And Firefox uses default_panel while Naver Whale uses default_page.

Going forward, we can define a merged API covering the aspects in each of these browsers. Have a meeting about it in which we invite both Opera, Naver Whale and potentially Vivaldi (they have non-extension web panels) to discuss directions and come to an agreement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementEnhancement or change to an existing featureneeds-triage: chromeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeproposalProposal for a change or new featuresupportive: safariSupportive from Safaritopic: sidebarDiscussions related to the sidebarAction and sidePanel APIs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions