On Web Extensions shortcomings and their impact on add-on security

Re:On Web Extensions shortcomings and their impact on add-on... by hawski on Sunday November 12, 2017 @01:45AM (#15679977)

Did they tell you how the extensions may conflict? I don't understand what it means. Couldn't it work like e.g. context menu does already for extension icon?

[ Parent | on HN ]

Re:On Web Extensions shortcomings and their impact on add-on... by eejdoowad on Sunday November 12, 2017 @06:16AM (#15680500)

What happens when two extensions try to place a widget in the same location? Chaos. Not that the status quo is any better.

Interestingly, Firefox's sidebar API only allows a single sidebar to be shown.

[ Parent | on HN ]

Re:On Web Extensions shortcomings and their impact on add-on... by drdaeman on Sunday November 12, 2017 @06:37AM (#15680532)

I still don't get it. What problem they're trying to avoid?

It's exactly the same if two extensions would currently try to manipulate the page by adding a frame (or, worse, a <div> with non-isolated UI) to the same location.

The only difference is, with out-of-page widgets (e.g. overlay regions or popouts), they won't be visible in the page's DOM.

[ Parent | on HN ]

Re:On Web Extensions shortcomings and their impact on add-on... by eejdoowad on Monday November 13, 2017 @03:49AM (#15685187)

My understanding is that if they do implement an API, they want it to be better than the status quo, not the same.

[ Parent | on HN ]