Live data from Hacker News

Google has removed the option to disable autoplay from Mobile Chrome

support.google.com

241–248 of 248 posts

Re: Google has removed the option to disable autoplay from Mobile Chrome

#241
post #238

Earlier quoted context omitted.

From a tech geek perspective, Firefox is the "emacs of browsers". They wrote a (lisp/js) interpreter and then wrote the (editor/browser) in that language. Unfortunately using a much more weakly-typed language [to write what is almost an OS of its own] yielded a mass of unmaintainable, constantly-mutating bloatware. They claim to be rewriting the interpreter layer in Rust, which is awesome, but 99% of the browser will…

Not sure where you're getting your information, but the majority of Firefox is written in C++, not Javascript.

https://www.openhub.net/p/firefox/analyses/latest/languages_...

The vast, vast majority of that C++ is legacy crud that gets #ifdef'ed out -- Mozilla development style seems to be to never remove code, ever; just #ifdef it out. Also there's a ton of boilerplate in there due to their homegrown IDL.

Re: Google has removed the option to disable autoplay from Mobile Chrome

#242

Earlier quoted context omitted.

SVG is smaller in a vast majority of those cases and looks better to boot

SVG can have non svg images inside of it. SVG has autoplaying animation possibilities. SVG has JavaScript if you are putting it directly into the body of the page. You can also put anything into SVG with the foreign object element, so also videos. So yes if someone stopped me abusing the users with my autoplaying videos I might decide to abuse them with SVG before these other options.

I didn't think about that. That's depressing.

Re: Google has removed the option to disable autoplay from Mobile Chrome

#243

Earlier quoted context omitted.

Restricting framerate will still download the 100mb GIF. Also, so many parts of websites use gifs and canvas. If you start blocking those, you'll be hiding loading spinners, menus and more. You're adding ton and ton of complexity and going at war after something pretty silly. If a website is abusive and does shitty things, just don't use the website. After some point, it's no longer the browsers job to babysit the we…

Canvas and gifs could be an opt-in feature on a per-website basis, just like notifications and webcam access.

With that logic, soon every single feature in the browser will have a pop up saying "Do you want to allow losing ?", "Do you want to allow use of "cursor css style?", etc.

Re: Google has removed the option to disable autoplay from Mobile Chrome

#244

(disclaimer: I work at Google, not on Chrome) The rationale here seems to be that by blocking video autoplay, Chrome incentivized sites shipping huge animated GIFs, or decoding video in JS and painting to canvas, both of which are very suboptimal for users. Another comment points to this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=106364... quote: Unfortunately, full autoplay blocking is counter prod…

Yeah but the sites that allow that garbage are 99% garbage. I want to block autoplay and can think of very very few things that slipped through. Particularly on news sites. I won't visit sites that allow stuff like that, and I'd bet that most people don't either. You shoudl optimize for those parts of your application that are most important and used most often. Amdahl's law

Re: Google has removed the option to disable autoplay from Mobile Chrome

#245
post #138

Earlier quoted context omitted.

Then maybe the solution is to also have the option turn off animated GIFs and perhaps frequent canvas repaints too; and not simply give up completely ! In any case, just leaving the option alone so at least it has some effect like it did before, would still be better than essentially a full surrender.

You can turn off GIF animation in Chrome, you are still downloading the giantass GIF. Slowing down canvas repaints if one of your overall goals is web applications that have feature and performance parity with desktop ones is, I think, unlikely. I'm a bit more surprised Google (and all browser vendors) aren't more proactive in just killing off animated GIFs.

That's why they suggest to use for replacing GIF.

Re: Google has removed the option to disable autoplay from Mobile Chrome

#246

Earlier quoted context omitted.

Yeah, which is why I stick with it even though they just butchered a few areas of the UI (most notably the home screen). Fortunately they seem to be listening to reviews and fixing things.

Does anyone know if there is a way in the new Firefox for Android to stop it from keeping my tabs open when I close the window without using "Quit"?

There is now an option to close tabs I think. After a time period like a day or a week. It's in beta

Re: Google has removed the option to disable autoplay from Mobile Chrome

#247
post #203

Earlier quoted context omitted.

Microsoft bundled Internet Explorer with Windows and made it impossible for users to remove it. That's not at all "pretty much the same thing."

Okay, do you care to address the core point of my comment? These are two examples of anti-competitive behavior. The details might differ, but the core idea of what they did and how they did it is the same (abusing their dominant position to anti-competitively disadvantage competitors). Yet Google gets a pass because "capitalism".

I've used Google search daily for many, many years now without ever feeling the need to use Chrome. I use Safari on my laptop and mobile Safari on my phone. I can't recall the last time I saw anything pushing me towards Chrome.

I'll take your word for it that these happens or happened, but I just tried a search in Safari and saw no Chrome ads.

Re: Google has removed the option to disable autoplay from Mobile Chrome

#248
post #43

Earlier quoted context omitted.

Sry for harassing here. If someone could look at the recent Android Webview v85 bug that has broken my app, that would be great. I raised a bug today for it https://bugs.chromium.org/p/chromium/issues/detail?id=112552...

>Sry for harassing here. If someone could look at the recent Android Webview v85 bug that has broken my app, that would be great. I raised a bug today for it https://bugs.chromium.org/p/chromium/issues/detail?id=112552... Asking on HN for a random chrome engineer using a fresh throwaway (created for this specific post) to look at your 11 hour old low priority performance bug for a specific piece of hardware seems mis…

That may be obvious to you. I had never filled a Chromium bug before and didn't know whether they were going to even have a look at it. Lookin g at the bug link you can see how widespread the damage was because of the recent update. It affected lots of people and its effects were that fps were down to 5 from 60 so yeah, pretty bad. Google doesn't really give a damn in certain areas (i.e. API) where their support is non existent unless you are sone type of VIP. So apologies for coming here with this, I guess I didnt know as much about Chromium bugs process as you do
Post reply on HN