In the browser itself, it has more capabilities that can overcome some *Google is now working on this problem in the browser*. I might as well answer the question once and for all: Why did I stop If something doesn't make sense, let me know. But, this isn't guaranteed to work because the page could run before the extension. The current method to deal with this is to add a shim (which essentially acts as an intermediary between the media and the page). This interface isn't capable of authenticating autoplay attempts. The JavaScript interface for media is identical for both extensions and pages.Therefore, it is possible for the page to end up working against the extension.
#Chrome autoplay video pcworld code
Determining if some media is autoplaying is difficult.Unfortunately, sites with obtrusive autoplaying are also sites with complex JavaScript code. JavaScript also knows when the user does anything in the page.In terms of media, JavaScript has direct access to media loading and playback control.JavaScript has low level access to mostly everything in a page: The complexity comes from the involvement of JavaScript. Such an algorithm takes time to engineer well and even more time to maintain and expand. More details for the reasons (also more technical)Ī good algorithm is a sophisticated algorithm. Now that Google's working on this problem, I have less of a reason to change my mind.I have other projects that I'm more interested in now, and other ideas that I want to explore down the road. What killed off the motivation was the lack of necessity I started this extension because someone I know requested it.Also, it takes a good chunk of time to respond to users on GitHub and the Chrome Web Store. (The more technical section explains in more detail). The amount of time it would take is much greater than the gain I can see.It was fun working on Disable HTML5 Autoplay for a while, but it became more mundane as time passed. Google acknowledges the audience that is dissatisfied with autoplaying (in fact, they reference Disable HTML5 Autoplay in the design document). In the long run, I believe Google will be able to design something that is sufficient for most users.However, the current design proposed has some limitations and lacks some granular control (they are discussed at the end of the design document).Because it's in the browser itself, it has more capabilities that can overcome some technical limitations of extensions (discussed more in the following section). Google is now working on this problem in the browser. I might as well answer the question once and for all: Why did I stop working on Disable HTML5 Autoplay? The main reasons EDIT: I should note that this is now referenced in other Disable HTML5 Autoplay documents for anyone to read.