> [...] However, one may simply wish to consume the fullscreen UI, not actually fullscreen the application [...]
> This PR implements a fullscreen inhibition feature in sway. When inhibited, sway will answer fullscreen requests correctly, but will not fullscreen the container.
I tried FF PiP recently, but I have "bspwm config honor_size_hints true" and that makes the window resize itself until it's the size of a postage stamp.
The above is a known bug in FF, though apparently fixed in FF73: https://bugzilla.mozilla.org/show_bug.cgi?id=1600414
For Chrome users, I was using the "Windowed - floating Youtube/every website" plugin to achieve the same effect. It also gives you the control UI, which PiP doesn't have yet.
This is not my experience. I see no added value in this PIP.
I use XMonad, which is a tiling window manager. I've always been able to put a video into applicative full screen, then switch the layout to whatever I want. E.g. 2 browsers windows each playing a borderless video.
Before XMonad, I remember that when I switched to another workspace/window and back, my browser window would have stopped being fullscreen.
I'd rather have Firefox not adding hacks to work around the flaws of mainstream window managers.
Getting the "normal" fullscreen is just two keyboard shortcuts away ("fullscreen" the program and assign its window the entire screen), rather than one. From an intuitiveness point of view, being able to hide a program's UI and change its window size separately is arguably more intuitive — according to the separation of concerns, the former is managed by the program itself and the latter by the WM.
PiP is really nice, but videos aren't the content for which getting a distraction-free experience is most important...
[0] I'm sure that it's also possible with other tiling WMs such as ratpoison, stumpwm, awesome etc.