Live data from Hacker News

Android 8.0 Oreo, thoroughly reviewed

arstechnica.com

51–60 of 130 posts

Re: Android 8.0 Oreo, thoroughly reviewed

#51
post #39
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.

I'd like to be able to tell my browser what it should tell the pages it's loading, especially if pages are leveraging it to do things against my will. That applies to blocking Google ads, as well as fixing Youtube malfeatures. Of course, it's understandable you won't see this from a browser paid for by Google. But you can't paint in broad brush strokes like "I don't think hiding side-effects or user actions helps any…

I'm disputing the fact there was a casual offhand design, and I don't think hiding the state of the render or the browser helps anyone not least developers who need the information about the state of their page.

I'm not saying that there can't be meaningful response from the browser to user hostile actions, I don't think anyone disagrees.

There's a broader question about a user's will and the sites intent especially when it comes to business plans of the site that I'm not sure if access to features native in the browser is aligned with say ad blocking or tracking etc... I don't know.

Re: Android 8.0 Oreo, thoroughly reviewed

#52
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…

Were you aware that Android has built-in tinting capability? It's under Display > Night Light. There's a quick tile for it too.

Re: Android 8.0 Oreo, thoroughly reviewed

#53
post #3

Keeping my fingers crossed that Project Treble is the real deal and would actually make it possible for a "generic AOSP image" to be installed on virtually any mobile device that came with Android. That's the dream, isn't it? But I think we've been burned too many times by Google's promises to "make it easier" for OEMs to update devices and other such promises, or at least these projects always sounded much better th…

> make it possible for a "generic AOSP image" to be installed on virtually any mobile device that came with Android

I would really love that. It would take the "how crappy is the vendor UI?" problem out of the equation when looking to purchase a phone.

Re: Android 8.0 Oreo, thoroughly reviewed

#55
post #31
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.

Is that something that can be done with a Chrome extension?

If not, then since Chromium is open-source, I imagine you could hack it in to a personal copy.

Re: Android 8.0 Oreo, thoroughly reviewed

#57
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.

Is that something that can be done with a Chrome extension? If not, then since Chromium is open-source, I imagine you could hack it in to a personal copy.

Chrome for Android does not support extensions.

Re: Android 8.0 Oreo, thoroughly reviewed

#58
post #49
post #45

Earlier quoted context omitted.

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.

Which Chrome for Android does not support.

Re: Android 8.0 Oreo, thoroughly reviewed

#59
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…

Were you aware that Android has built-in tinting capability? It's under Display > Night Light. There's a quick tile for it too.

I think this is vendor implemented (or maybe vendor crippled). It does not appear on Huawei android 6.0

Re: Android 8.0 Oreo, thoroughly reviewed

#60
post #51
post #39

Earlier quoted context omitted.

I'd like to be able to tell my browser what it should tell the pages it's loading, especially if pages are leveraging it to do things against my will. That applies to blocking Google ads, as well as fixing Youtube malfeatures. Of course, it's understandable you won't see this from a browser paid for by Google. But you can't paint in broad brush strokes like "I don't think hiding side-effects or user actions helps any…

I'm disputing the fact there was a casual offhand design, and I don't think hiding the state of the render or the browser helps anyone not least developers who need the information about the state of their page. I'm not saying that there can't be meaningful response from the browser to user hostile actions, I don't think anyone disagrees. There's a broader question about a user's will and the sites intent especially…

> There's a broader question about a user's will and the sites intent especially when it comes to business plans of the site

The site's business plans are not my problem. Basically, my phone and my computer should do what I want. Why is there even an API to make a video player enter/exit full-screen mode ? That's 100% a user decision and there is no valid reason why that should ever be exposed to JS.

Post reply on HN