Jabis Sevon

This is again due to no user interaction to start/read the cameras and whatnot - why the camera selectors should be behind a click - we can join with defaults...

the `muted` attribute is either forced or then additional enabled=false gets introduced - so the other party needs to right click the video, enable controls and uncheck mute from the...

Hmm Firefox does not expose the .requestPictureInPicture as a method to the DOM, so this could be construed as a bug. In FF you need the `media.videocontrols.picture-in-picture.enabled` to be true...

This check fails on FF, even though PIP **will** get executed, but it throws an error still in the DOM which leaves further JS execution in limbo, which is why...

Ha, the browser's fullscreen api doesn't respect Web-Api, double clicks go thru underlay - only way would be to disable all pointer-events and construct all the controls by ourselves -...

OK some more info, apparently the Firefox PiP also discriminates based on if `srcObject` is a media stream or not - meaning when we instantiate a video without having a...

And what I said [here](https://github.com/meething/meething/issues/79#issuecomment-620898843) did **NOT** work in any shape or form :(

Buttons and whatnot just wont work on MediaStream - I have forced browser PiP button visible but it just will not do anything - also the documented `'PictureInPictureEnabled' in document`...

@Dletta your own camera(User initiated) is Firefox pip-able, other connections come with MediaStream objects, (Not user initiated) thus Firefox non-pip-able

uhm I might have been too fast to say even that's pipable, as that's exactly what we're doing for the local video and firefox doesn't PiP even that :D regular...