tangentially related: what's everyone's solution for blocking autoplaying sticky videos? By that I mean the kind that usually shows up on news sites or tech blogs. It usually manifests as a "recommended" video that's totally unrelated to the article at hand, and stars playing without you clicking the play button. If you scroll past the video, many of them convert to a sticky mini player that stays around wherever you…
Google has removed the option to disable autoplay from Mobile Chrome
181–190 of 248 posts
Re: Google has removed the option to disable autoplay from Mobile Chrome
#182I don't get why Firefox's market share is still so low when compared to Chrome's. I get why FF fell behind over the last decade, but since Firefox Quantum those reasons have largely disappeared.
I wonder more about why people accept their anti-competitive behavior when Microsoft was shafted for doing pretty much the same thing.
Re: Google has removed the option to disable autoplay from Mobile Chrome
#183This is weird. They see the general tech community slowly turning against them and they double down on all the wrong things they were doing that caused the negativity.
The general tech community is a tiny fraction of their user base, though. Put simply, they don’t care.
It feels like they are just force-feeding the 'UX features' of Chrome and ignoring all the feedback from the tech community.
Things like truncating url sub-domains and hiding the url address bar with dynamictoolbar are not necessarily wrong features. However, to me they should always be opt-in, they should never be fixed defaults as what we have now in the latest upgrade of Firefox for Android.
Firefox used to be about freedom and customization. If I want to break it by messing with about:config then I should be able. If I want to break it with a non-compatible add-on then I should be able to. This whole UX mindset of padding the room and "we know better than you what you should want" feels very dismaying especially for a project that exists because of community contributions.
Re: Google has removed the option to disable autoplay from Mobile Chrome
#184(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…
The GIF/Canvas problem is something critics brought up when Chrome first introduced its automatic autoplay blocking. Chrome's autoplay blocking didn't go far enough to block all media types, and it had fundamental design flaws that made it easy to circumvent and easy for websites to detect when a video is blocked. Blocking autoplay was never about saving data -- there were always going to be these kinds of circumvention techniques. Data-saving solutions require different strategies.
But because ultimately Chrome just wanted to do its own thing and get those positive press releases, and because the Chrome devs were trying to fix multiple unrelated problems at the same time, we got a really weird Frankenstein implementation instead of something sensible like auto-muting browser tabs on new domains by default. This is a result that could have been avoided by engaging more with the web community and spending more time up-front thinking about how the feature was going to be used in the wild. Instead it got rushed out because the Chrome dev team digs in its heels and gets combative whenever developers question their decisions.
This result is especially frustrating with autoplay, because digging in heels and rushing the implementation didn't just leave us with a useless feature -- it broke functionality on a ton of websites, including Google's own search page. We got a hacky solution that was rolled out too early and that broke the web because Google insisted they needed an behaviorally-driven, complicated system with a bunch of weird rules and exceptions about when things would and wouldn't be able to play.
And now all of the minor benefits from that system are getting removed and all of the justifications for breaking existing sites are apparently being rolled back -- but we're still left with a hacky solution that breaks websites. We got the worst of all possible worlds because the Chrome team is apparently just unable to engage with developer communities.
As a web dev, I am low-key bitter about how this all played out. This is exactly why it's a bad idea to give the Chrome team so much outsized control over web standards. They broke almost every indie web game online, forced multiple engines to release updates, and this is what we're left with? Because nobody on the Chrome team was capable of predicting that advertisers were going to start shipping GIFs?
Re: Google has removed the option to disable autoplay from Mobile Chrome
#185Earlier quoted context omitted.
Most normal companies are okay with small divisions. Sometimes they'll sell them off. It feels like Google is like Intel. They reflexively kill anything that isn't going to be worth a few hundred million in revenue.
Alphabet has a revenue per employee of $1.5M. In order to keep that number they need big hits. That's why small products just get abandoned / die.
That's less than $3 per user. Google can't squeeze $3/year in ad revenue out of a product used primarily by wealthy plugged-in tech types?
Re: Google has removed the option to disable autoplay from Mobile Chrome
#186Earlier quoted context omitted.
BigG couldn't do that (disable other user hostile media) because it would interfere with ads. Now I'm looking for a gif and canvas blocker for FF mobile. Any hints on how to tune uBO?
You can't turn off gifs or canvas because it would just break too much internet. I could imagine and equal reaction thread here if google deemed some gifs and canvas uses "unworthy" and were blockable.
Individuals must have the ability to shape the internet and their own experiences on it.
Re: Google has removed the option to disable autoplay from Mobile Chrome
#187Re: Google has removed the option to disable autoplay from Mobile Chrome
#188They're not about to make their own product limit their own whims!
Re: Google has removed the option to disable autoplay from Mobile Chrome
#189tangentially related: what's everyone's solution for blocking autoplaying sticky videos? By that I mean the kind that usually shows up on news sites or tech blogs. It usually manifests as a "recommended" video that's totally unrelated to the article at hand, and stars playing without you clicking the play button. If you scroll past the video, many of them convert to a sticky mini player that stays around wherever you…
DNS-over-HTTPS adds a few kinks to this but does not prevent the inherent concept.
Re: Google has removed the option to disable autoplay from Mobile Chrome
#190Earlier 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…
SVG is smaller in a vast majority of those cases and looks better to boot
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.