[GeneticGenesis]

Mozilla's choice to add their own pip button is a massive pain for anyone developing video applications - anywhere over the player can't be considered a safe space to add our own buttons anymore, it really feels like Mozilla didn't talk to any video service developers when deciding how to approach this problem.

Pip needs to be common API driven (as Chrome is) to make building portable video applications possible.

A terrible misstep from Mozilla. (And yes, this has been repeatedly raised on the bug tracker with no answer)

[mrpopo]

> Pip needs to be common API driven (as Chrome is)

Ah yes, Mozilla should follow the steps of Google's web experiments playground, the Chrome browser. Every month we hear about a new self-serving feature implemented by Google/Chrome engineers.

The web is slowly drifting to the IE days again, and of course this move by Mozilla doesn't help it, but let's not forget the bigger culprit.

[thrtythreeforty]

Maybe this is inconvenient for developers, but as a user, it feels awesome to know that the browser is technically capable of doing something, and does it when I ask, not at the behest or limitation of the PiP API. You know YouTube/Google would put this feature of my browser behind a Premium paywall.

So much of the modern web is "run your code on my computer," so this feels nice, where the browser is my tool to browse the web.

[hombre_fatal]

The other browsers have it implemented as an extension that adds a button to the browser's chrome which I think is a better place. I too think it's a bit ham fisted to inject UI like this. Though I admit that Firefox's impl is obvious to the average user where a new, vague button icon in the browser's chrome is not.