Google show signs of reconsidering auto mute after developer critique
1–10 of 56 posts
Re: Google show signs of reconsidering auto mute after developer critique
#2I'm not sure I saw any signs that they're "reconsidering" on this ticket -- just that they're now aware of how many corner cases they have.
I can easily see Google saying, "eh, that's your problem, learn to whitelist your site with us."
Re: Google show signs of reconsidering auto mute after developer critique
#3I'm not sure I saw any signs that they're "reconsidering" on this ticket -- just that they're now aware of how many corner cases they have. I can easily see Google saying, "eh, that's your problem, learn to whitelist your site with us."
That's not my interpretation of their comments at all.
#55 "Chrome Product Manager for desktop here. Thank you for posting these examples, they're superful helpful to the team. We didn't intend to break all this awesome existing content that relies on webaudio, and we are investigating paths forward now. More updates will follow on this bug."
Re: Google show signs of reconsidering auto mute after developer critique
#4What I don't understand is why they went this convoluted route of trying to assess what's legitimate or not, what's a user interaction or not. Does anyone know why they didn't go the route of other permissions like notifications or location, with a discrete popup that says the page is attempting to play some audio (or video), do you want to allow? If it is legitimate, the user clicks allow once and the site works forever.
Re: Google show signs of reconsidering auto mute after developer critique
#5Usually when a major web browser decides to do something that has the potential to break existing websites they do extensive testing and put the call out for dev feedback before they release. Why didn't that happen here?
Also it's odd that Chrome decided to explicitly whitelist some sites. Surely that's an admission that their automated workflow doesn't actually work well?
Re: Google show signs of reconsidering auto mute after developer critique
#6I would suggest just having the tab muted by default, and maybe an easier button to toggle on/off, than current right-click, to unmute/solo. Perhaps, a limited notification for the first 100 times your tab is muted and it detects sound being played in the tab, so you're not wondering why no sound is playing.
Re: Google show signs of reconsidering auto mute after developer critique
#7Since JavaScript can generate moving imagery, and animated GIFs can as well, the only sensible thing is to consider the video as something conceptually different from audio. I wouldn't mind if they always allow videos to play, except I want full control over the audio at all times.
Re: Google show signs of reconsidering auto mute after developer critique
#8What I don't understand is why they went this convoluted route of trying to assess what's legitimate or not, what's a user interaction or not. Does anyone know why they didn't go the route of other permissions like notifications or location, with a discrete popup that says the page is attempting to play some audio (or video), do you want to allow? If it is legitimate, the user clicks allow once and the site works for…
Because they sell ads, some of them video ads.
Re: Google show signs of reconsidering auto mute after developer critique
#9What I don't understand is why they went this convoluted route of trying to assess what's legitimate or not, what's a user interaction or not. Does anyone know why they didn't go the route of other permissions like notifications or location, with a discrete popup that says the page is attempting to play some audio (or video), do you want to allow? If it is legitimate, the user clicks allow once and the site works for…
They probably wanted to avoid "breaking" major sites like Youtube, Spotify, and Soundcloud, and tried to create a smarter whitelist system.
Re: Google show signs of reconsidering auto mute after developer critique
#10I'm not sure I saw any signs that they're "reconsidering" on this ticket -- just that they're now aware of how many corner cases they have. I can easily see Google saying, "eh, that's your problem, learn to whitelist your site with us."
That's not my interpretation of their comments at all. #55 "Chrome Product Manager for desktop here. Thank you for posting these examples, they're superful helpful to the team. We didn't intend to break all this awesome existing content that relies on webaudio, and we are investigating paths forward now. More updates will follow on this bug."
that's corporate talk for "we don't care, let's stall and come with even more fucked up solution"