Apple Safari, Chrome, Edge browser, Firefox, Information Security, Mozilla, Privacy, Top News, video autoplay

Firefox 66 will silence autoplaying web audio

Quieter web browsing is finally within reach for users of Mozilla’s Firefox.

It’s been on the to-do list for a while, but a new blog by the company has confirmed that from Firefox 66 for desktop and Firefox for Android, due on 19 March, media autoplay of video or audio will be blocked on websites by default.

According to Mozilla’s developer blog, this means:

We only allow a site to play audio or video aloud via the HTMLMediaElement API once a web page has had user interaction to initiate the audio, such as the user clicking on a ‘play’ button.

Until the user does something to initiate a video or audio stream, the only thing that will be possible is muted autoplay.

If you find it annoying when videos starting of their own accord, this will come as a welcome news. But what about use cases where it’s desirable?

Currently, it is possible to achieve autoplay blocking by toggling a setting from about:config (type that into your Firefox address bar), but that is a global setting and is either on or off.

Under the new regime, there are several options: enabling autoplay once on a website, white-listing websites to always allow autoplay from those sites, or always allow or block autoplay for all websites.

Audio conundrum

When it comes to media autoplay blocking, version 66 seems to be the number to aim for – Google implemented a similar default setting with Chrome 66 in April last year.

Apple has had default blocking since June 2017, while Microsoft offered the ability for users to turn off autoplay last summer (i.e. it’s an option rather than a default).

One thing Firefox doesn’t yet block is audio that is enabled through the JavaScript Web Audio API used by many older games and web apps.

Stated Mozilla:

We expect to ship with autoplay Web Audio content blocking enabled by default sometime in 2019.

It’s an area where browser makers have to tread carefully, as Google found out to its cost when it included Web Audio API blocking by default to Chrome 66 and was assailed with complaints about broken software.

Source : Naked Security

Previous ArticleNext Article

Send this to a friend