Live data from Hacker News

Building Firefox's Picture-in-Picture Support

hacks.mozilla.org

31–40 of 133 posts

Re: Building Firefox's Picture-in-Picture Support

#31

For the life of me I can't see why anyone would need picture in picture for browsers. More features most people don't need. Please come down to earth Mozilla. You have lost your way. Please revisit NCSA Mosaic and witness your roots.

I use it a lot because I have only one monitor.

Couldn't you just open it in a new window and resize/tile your existing windows?

Re: Building Firefox's Picture-in-Picture Support

#32
post #14

Earlier quoted context omitted.

I use PIP a lot in Chrome while browsing Reddit. If I see a video link, I can play the video while continuing to scroll through Reddit comments. (YouTube PIP is kind of difficult to discover; you have to right-click, move the mouse off the menu, and right-click again to get the native right-click menu, which is where the PIP button is.)

Why not just open it in another tab?

You mean open in another window, arrange and resize that window to not get in the way while making the video visible, hoping that the website layout doesn't make that close to impossible, and still not easily being able to have it stay on top of the window you interact with... instead of a single click that does the right thing?

Re: Building Firefox's Picture-in-Picture Support

#33
> Given that it would be available on any video content, the feature needed to be discoverable and straight-forward for as many people as possible.

This is the designer’s nightmare: Every feature needs to be available to everyone, therefore be visible on the screen. Yet they only cite rare usecases: « Watching sports event while continuing to browse the web ». In the meantime, the blue tone isn’t generally consistent with the websites’ colors.

I would have supposed moderatelt-used features belongs in the right-click menu like the rest, or they need to find a way to merge it with the video controls (I guess an Apple designer would imagine a new kind of special press to detach the video, which is fine too).

Re: Building Firefox's Picture-in-Picture Support

#34
post #13

Picture in Picture is great for lectures or follow-along tutorials and I'm glad people are taking it more seriously (initially was using Youtube on Safari purely because of this feature, but later on Chrome had it... albeit a bit wonky, I started using it on Chrome normally).

I would love to have an external controller for start/stop/fast forward/rewind when watching tutorials on Youtube. For example a controller [1] people are using to edit videos. Quite often I would like to pause the video for a while, repeat last 30 sec or by-pass some boring segment. [1] https://www.amazon.com/Contour-Design-Shuttle-Xpress-Multime...

That is an awesome idea. Would be extremely useful for guitar and transcription too, while writing the text in Word.

It typically would be a usecase for the Macbook touch bar, does anyone has one and can tell us whether it has an integration with web videoplayers?

Re: Building Firefox's Picture-in-Picture Support

#35

> To work around these problems, we rely on the fact that the web page is being sent events from the browser engine. At Firefox, we control the browser engine! Before sending out a mouse event, we can check to see what sort of DOM nodes are directly underneath the cursor. This triggered some mental alarm bells when I read it. I understand what Mozilla is trying to accomplish, but this feels like it could become a ser…

A Web developer is never going to see this. The events mentioned are being sent to the Shadow DOM which implements the PiP UI (as well as the default video controls UI), not the webpage.

Re: Building Firefox's Picture-in-Picture Support

#36
post #18

> To work around these problems, we rely on the fact that the web page is being sent events from the browser engine. At Firefox, we control the browser engine! Before sending out a mouse event, we can check to see what sort of DOM nodes are directly underneath the cursor. This triggered some mental alarm bells when I read it. I understand what Mozilla is trying to accomplish, but this feels like it could become a ser…

I don't think they are talking about mouse events the website can observe. Firefox needs to figure out where the video is and make it's UI on top of that work, there is no observable interaction with the site DOM or its event handlers.

The post says that the video element is told it's being hovered, although it is unclear if that means the rendering context has that element set to hover (thus CSS changes even if pointer events is set to none), or that some internal-to-the-browser state is set to hover for the video.

Re: Building Firefox's Picture-in-Picture Support

#37
I have to say I love this feature and have so since the first time I encountered it in my Firefox Nightly installation a few months ago (on Windows).

Glad to also have it available on Linux and Mac now. It's perfect for on-the-side Youtube videos.

Re: Building Firefox's Picture-in-Picture Support

#38

With (some) television sets in mind that popularized (for, um, me at least) the picture-in-picture term as one channel of video on top of another channel of video, it feels weird that the term is here used when only a minimum of 1 videos is involved...

I feel the same way. This is just a new way of windowing the content, not displaying 2 different sources in one screen.

I've seen a couple of this breaking the video out of the main layout, but not sure if it was this Firefox feature or not. I was pretty sure that once the video broke out of the normal layout, the original location of the video was replaced with ads playing without audio. I was immediately turned of by it.

Re: Building Firefox's Picture-in-Picture Support

#39
post #15

Earlier quoted context omitted.

A comment on reddit said they use it all the time when following coding tutorials. Seems like a handy use case.

That brings up a second question: who watches coding tutorials? I'd imagine it's probably people with less than a few weeks of coding experience, because it's horribly inefficient compared to text tutorials.

One of my few very good teachers in school highlighted that people learn differently - some people by reading, others doing and others again watching. I'm most definitely somewhere between the last two. I find that for me watching high quality tutorials (pluralsight, CBTNuggets, etc) at 1.5-2x speed is a very good way to get introduced into a language particularly when I seed a solid foundational understanding rather than knowing exactly how to add an additional command into npm run, etc.
Post reply on HN