WELCOME

to the house of Harry Plopper

For now, though, there seems to be no sign that

For now, though, there seems to be no sign that anything significant changes to the way audio is played will be implemented. Most of the major features are expected to be implemented with Firefox 67, and, even then, those changes will be gradual.

There's only one problem with this plan: it still does not include a way to automatically toggle audio out of the game. The new "pause audio" option is there, but if you're going to use it, you'll want to ensure you're not using the device that's currently playing a video.

Mozilla has promised that it will support this feature in Firefox 67. This means that in a few weeks, the new "pause audio" option will be enabled. In the meantime, the current plan is to disable it at all, but it should be there by the end of the year.

This is not the first time Mozilla has made this change. In March, Google announced that it would be rolling out new support for auto-pause audio, but the timing for this change is unclear: Google's system doesn't allow for some automatic media playback, so it's likely that this won't be a major feature, but it does seem likely to add a benefit. It was possible that this would only be a feature, but maybe not.

The problem remains, however, whether or not this will be implemented in Firefox. In a post on Reddit, the developer of Chrome says that the idea that it will eventually be used for things like video compression has become "a bit ridiculous." Perhaps the new "pause audio" option will make it easier for developers to do this. But, as a developer, I'm very hesitant to give up on using this feature, especially when the system is so good.

What about YouTube? It's still an open question. Google's announcement that it will be adding video autoplay support to its YouTube app has many people wondering whether video autoplay is necessary for YouTube to make videos.

Comment an article