You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is an affordance in place for extensions so that they can embed frames with web origins in extension pages, which will then be treated as first-party. (Reference)
The current affordance however requires an extension to have host_permissions over the web origin.
If the web origin belongs to the extension author, in most cases it wouldn't need or request host permissions since it can directly communicate with the page using sendMessage having declared it as externally_connectable in its manifest.
Having minimal permissions in this case harms the experience since the scenario doesn't fit into the current affordance.
Q: Can we consider extending the affordance to consider frames first party on extension pages if the extension has the embedded webpage origin declared as externally_connectable in its manifest?
The text was updated successfully, but these errors were encountered:
Currently there is an affordance in place for extensions so that they can embed frames with web origins in extension pages, which will then be treated as first-party. (Reference)
This is true for Chrome's implementation but I'm not sure how other browsers treat extensions. At the very least, it would be good to file this as a feature request at crbug.com/new.
Currently there is an affordance in place for extensions so that they can embed frames with web origins in extension pages, which will then be treated as first-party. (Reference)
The current affordance however requires an extension to have
host_permissions
over the web origin.If the web origin belongs to the extension author, in most cases it wouldn't need or request host permissions since it can directly communicate with the page using
sendMessage
having declared it asexternally_connectable
in its manifest.Having minimal permissions in this case harms the experience since the scenario doesn't fit into the current affordance.
Q: Can we consider extending the affordance to consider frames first party on extension pages if the extension has the embedded webpage origin declared as
externally_connectable
in its manifest?The text was updated successfully, but these errors were encountered: