Android 8.0 Oreo, thoroughly reviewed • Hacker News Board

Re: Android 8.0 Oreo, thoroughly reviewed

#41

Post by Mindwipe » Tue, Sep 05, 2017, 12:39 PM UTC

kuschku wrote: post #31

kinlan wrote: post #21

Earlier quoted context omitted.

Shared below too. Just as a quick point and I will drop it in the article comments too. I'm the lead for our Chrome Developer Relations team. Chrome doesn't disable picture in picture for Youtube, Youtube disable it in Chrome. They listen to resize events iirc and then exit fullscreen mode (the only way to currently get to pip mode in Chrome).

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.

Re: Android 8.0 Oreo, thoroughly reviewed

#42

Post by Mindwipe » Tue, Sep 05, 2017, 12:40 PM UTC

sdotsen wrote: post #30

Can anyone confirm if they brought back the ability to select a wifi/Bluetooth connection via a drop-down from the swipe down option? You know, without having to click and go into the screen to select the device you want to connect to.

They did (I don't think it was ever gone as such, they just messed up the gesture, but it's back).

Re: Android 8.0 Oreo, thoroughly reviewed

#43

Post by izacus » Tue, Sep 05, 2017, 12:44 PM UTC

Mindwipe wrote: post #41

kuschku wrote: post #31

Earlier quoted context omitted.

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.

Most of YouTube content isn't music though. Why are they so user hostile - e.g. why can't I listen to talks/podcasters in the background while browsing the internet?

Re: Android 8.0 Oreo, thoroughly reviewed

#44

Post by izacus » Tue, Sep 05, 2017, 12:46 PM UTC

grepthisab wrote: post #36

Jedd wrote: post #20

After my Pixel updated recently to Oreo, being frustrated by a constant notification for Twilight (a red-tinting background app) and starting to search on google for a solution -- I discovered quite a lot of people have been asking 'how to suppress notifications on oreo' recently. FWIW you can control the notification snooze timeout, but you're going to need Tasker [1] (or similar). Interestingly I evidently bought t…

In the middle of updating my Pixel XL, use Twilight daily. Will it still work after the update?

Pixels have a built-in tinting mode which actually does filtering on compositor level. What does Twilight add to that?

Re: Android 8.0 Oreo, thoroughly reviewed

#45

Post by kuschku » Tue, Sep 05, 2017, 12:52 PM UTC

kinlan wrote: post #34

kuschku wrote: post #31

Earlier quoted context omitted.

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

So you would like us to not tell the page what the render is doing? I'm not sure how that would play out for any number of API's that exist on the web. Developer's have consistently had the means to override the default actions of the browser (think drag and drop) but I don't think hiding side-effects or user actions helps anyone.

Actually, yes. I want that the user is able to force a page to do whatever the user wants, if they choose to do so.

Just like my browser blocks popups, and my browser blocks those sites that try to prevent right-click, and my browser blocks those sites that spawn dialogs when you try to leave them, Just in the same way I want my browser to force websites to allow PiP.

Re: Android 8.0 Oreo, thoroughly reviewed

#46

Post by arjie » Tue, Sep 05, 2017, 12:52 PM UTC

izacus wrote: post #43

Mindwipe wrote: post #41

Earlier quoted context omitted.

That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.

Most of YouTube content isn't music though. Why are they so user hostile - e.g. why can't I listen to talks/podcasters in the background while browsing the internet?

If you're in the US, you can do that with Youtube Red.

Re: Android 8.0 Oreo, thoroughly reviewed

#47

Post by kuschku » Tue, Sep 05, 2017, 12:53 PM UTC

Mindwipe wrote: post #41

kuschku wrote: post #31

Earlier quoted context omitted.

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.

That’s their problem. A browser should always give a user the upper hand.

Browser block popups, forcefully enable right-click on sites that disable it, browsers allow users to forcefully enable zoom, or background playback.

And just like that, browsers should also allow users to forcefully enable PiP.

Re: Android 8.0 Oreo, thoroughly reviewed

#48

Post by avaer » Tue, Sep 05, 2017, 1:03 PM UTC

arjie wrote: post #46

izacus wrote: post #43

Earlier quoted context omitted.

Most of YouTube content isn't music though. Why are they so user hostile - e.g. why can't I listen to talks/podcasters in the background while browsing the internet?

If you're in the US, you can do that with Youtube Red.

Amusingly, this does answer the parent question.

Re: Android 8.0 Oreo, thoroughly reviewed

#49

Post by annnnd » Tue, Sep 05, 2017, 1:06 PM UTC

kuschku wrote: post #45

kinlan wrote: post #34

Earlier quoted context omitted.

So you would like us to not tell the page what the render is doing? I'm not sure how that would play out for any number of API's that exist on the web. Developer's have consistently had the means to override the default actions of the browser (think drag and drop) but I don't think hiding side-effects or user actions helps anyone.

Actually, yes. I want that the user is able to force a page to do whatever the user wants, if they choose to do so. Just like my browser blocks popups, and my browser blocks those sites that try to prevent right-click, and my browser blocks those sites that spawn dialogs when you try to leave them, Just in the same way I want my browser to force websites to allow PiP.

I agree with you, but that is probably something that belongs to a plugin.

Re: Android 8.0 Oreo, thoroughly reviewed

#50

Post by andrepd » Tue, Sep 05, 2017, 1:09 PM UTC

izacus wrote: post #43

Mindwipe wrote: post #41

Earlier quoted context omitted.

That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.

Most of YouTube content isn't music though. Why are they so user hostile - e.g. why can't I listen to talks/podcasters in the background while browsing the internet?

Use Newpipe, now you can.