See @mcclure111's tweets today for an example.
-
-
-
There's way too much to figure out what core problems are. Lots of claims that unmaintained sites won't work. Isn't there some way to just manually click a local link or allow sound on the site?
-
That doesn't work if you have predicated your design on people not having to do that.
-
I'm sympathetic with frustration at how badly they seem to have violated least-surprise, & pro-YT bias. But this is also a browser revisiting their bad choice to act as publisher-agent over user-agent.
-
Would artists be happy if it were a "this site wants to play sound - yes/no/always" prompt and YT had it too?
-
If the site had a "can this site play sound?" popup, or if it were even *possible* to slip a <script src="chromeAutoplayWorkaround.js" /> into the top of the page, I'd be ecstatic. The design of the feature inhibits the creation of such a chromeAutoplayWorkaround.js.
-
Frankly, I've always wanted a sitewide mute button for http://dryad.technology and I just haven't had the time to implement one. If the browser did it FOR me? Awesome.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.