News for hackers. Stuff that matters.

A comment on State of web browsers in 2018. Parent comment

Re:State of web browsers in 2018 by dmitriid on Thursday December 06, 2018 @01:01PM (#18620415)
A recent example is how Chrome broke audio on a lot of websites https://www.theverge.com/2018/5/15/17358752/google-chrome-66...

I won't even link to the discussion in Chrome's bugtracker, Chrome team didn't even test the change, apparently.

They also actively build "Chrome-only" websites.

[ Parent | on HN ]
Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @02:12PM (#18621074)
The Chrome audio thing really, really bothers me.

The change broke a ton of neat, interesting games that are never going to be updated. And given Google's aggressive autoupdates, running an older version of Chrome to experience a specific old website is non-trivial.

The change signals a blatant disregard for preserving pieces of art, culture, and shared history.

[ Parent | on HN ]
Re:State of web browsers in 2018 by untog on Thursday December 06, 2018 @02:29PM (#18621232)
IMO that's not an abuse of monopoly thing at all. It's not as if removing auto-play audio will push users towards some Google-only product, if anything it would mean fewer users choosing Chrome.
[ Parent | on HN ]
Re:State of web browsers in 2018 by kiriakasis on Sunday December 09, 2018 @06:14AM (#18640328)
Disagree. It can be a push for web developers and amateur site-buildign-people-that-have-not-that-much-interest-in-the-web-shenanigans to use google-approved APIs.

Not by promoting google as better but by simply promoting a view of google-web and other-web.

[ Parent | on HN ]