11–20 of 133 posts
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.
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.
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.
(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.)
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.
A comment on reddit said they use it all the time when following coding tutorials. Seems like a handy use case.
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 serious WTF moment for a developer. "There is absolutely no way in hell this element should be able to receive mouse events right now, what is Firefox doing?"
Is this a problem? Perhaps the web is so far down the hacks/exceptions route that adding one more legitimately won't make a difference?
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.
> 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…
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.
it allows me to size video frames arbitrarily across streaming sites like CyTube that don't support frame-out natively.
As someone who had to use mosaic and gopher and all that shit, i'd really rather not revisit it. It's nice in the way that it's sort of quaint to boot up an old workstation that has nothing but QBASIC, but it's not actually pleasant or useful.