Add Firefox support
Piter432 opened this issue · 17 comments
Like in title. Of course, if it's necessary
Yes, it's still necessary. Unless the situation has changed, Firefox's media.autoplay.enabled will simply prevent untrusted play() invocations on all pages, which can send media players to bad states (they expect events to be fired or property values to change). Also, there's no way to control which pages will have autoplay disabled.
To quote the README:
Firefox will be supported when WebExtensions has matured enough to support all the features necessary.
I took a quick look just now, and WebExtensions supports mostly everything that's needed for the extension to work. I'll hold off on this until I've finished version 0.8 first. By then, the extension will be able to stop autobuffering.
any eta on this?
@xxcriticxx Not sure yet. Maybe after version 0.8.
and what version we in right now?
@xxcriticxx The latest version can be found on the releases page. Planned changes for each new version are grouped under milestones. Version 0.7 will most likely take more time to do than 0.8.
thx for info keep up great work
Setting media.playback.enabled to false does the job, so why bother doing the same thing via an addon ?
You can access that setting via about:config page in FF.
@uBlock-user: I know about that switch in about:config. Also, I know a lot about about:config. I mean I have heavily modified Firefox on my old PC (yes, I have lot of powerful extensions and Firefox doesn't slow on my old PC in opposite to Chrome with much lower number of Chrome's extensions, while lot of them isn't very powerful, if you know what I mean).
Btw., this switch disables auto play on ALL websites, if I need to enable auto play temporary I need to switch it to true and refresh the page if the setting didn't work without doing refreshing the page. The way that I can disable/enable auto play on the page in this extension is better. Not the best (there should be something like in dynamic panel in uBlock Origin for users who turn on advanced features of uBO), but better than setting this switch in about:config to true/false.
@Piter432 i think you can do this with uMatrix
Btw., this switch disables auto play on ALL websites, if I need to enable auto play temporary I need to switch it to true and refresh the page if the setting didn't work without doing refreshing the page.
Yes, In that case, you will need an extension. You didn't mention this in the original message or anything of that sort and no one said anything about this switch so I presumed none of you knew about it.
Anyways for me, that switch did the job, so I shared the info here. Also this extension is fabulous and the only extension I know that was able to stop BRIGHTCOVE players from making multiple attempts to invoke the autoplay on Comicbook.com. That website is riddled with these players on all articles.
Someone already made an extension for FF - https://addons.mozilla.org/En-us/firefox/addon/disable-autoplay/
Try and see if it works or not.
Someone already made an extension for FF - https://addons.mozilla.org/En-us/firefox/addon/disable-autoplay/
I briefly looked at the code and it seems YouTube-specific right now. I don't see any code that is supposed to work for all websites.
Sure this extension doesn't quite work the way it should on many websites, but it works better than disabling JavaScript or HTML5 media completely, which is sure to break all websites. Eventually I do plan to add a more advanced language to control the extension's behavior much like uBlock Origin.
Unfortunately I don't have an ETA when any major development is going to happen again. I have many priorities outside of my two popular GitHub projects (this is one of them), and for the time being, I feel like diverting my limited time to ungoogled-chromium of the two projects. This doesn't mean I'm abandoning Disable HTML5 Autoplay though; that I am sure of.
Hey great job so far, I'm loving the Chromium extension, these new players were making it worse for folks like me who are on limited data plans and hate the annoyance of a video starting on its own everytime you refresh a page or turn to another article. Adding the pre-load feature will be an absolute bonus though, so I hope you do that soon.
Confirmed on the Aurora branch - ie. 53.0a2 (2017-02-05) (64-bit) the option is media.autoplay.enabled which needs to be set to false as stated by Eloston, so far as I can see the option provided by uBlock-user is either deprecated, obsolete or no longer used. For clarity people should check.
Such a shame we need an extension for this and even need to wait more than 1 year to have it in FF. (No offense my frustration is for this awful auto-play trend and browsers which don't give you proper control over it)
I have managed to wrangle it on Firefox functionally using a combination of about:config settings/toggles but yes it is a shame that every new technology has to be so abused that it either dies, never reaches it's potential because it alienated the base, or simply turns dysfunctional like Flash. If people weren't in such a rush to shove their crap in your face so rudely that they don't even care if you want or are ready for it, then there would be no need; but alas shame and integrity are endangered species.
So hopefully in the meantime we can provide some counterbalance to the devolution that is ruining our lives. As for why it is not available for Firefox yet. Unless people are aware of solutions and willing to take time to contribute them; they need to just acknowledge that those who do take it upon themselves to do it are facing many obstacles, the least of which is the lack of proper API often or simply that they don't have the time and/or resources to play cat and mouse with companies whose sole existence is to push things out.
Additionally, consider the specifications for HTML5 are not even final or redundant yet across platforms (more like frameworks) that each provider uses. The implementations are by no means consistent. That alone makes any cross browser single solution difficult if not impossible. There will always be some compromise on the extent of a feature due to the browser's limitations - be it by policy or by lack of developed or robust API.
The implementations are by no means consistent. That alone makes any cross browser single solution difficult if not impossible.
There is some discussion to fork and modify uBlock Origin as a basis for the 0.7 rewrite. That will solve most of the incompatibility issues I believe. If not, it will make porting to Firefox easier (as Chrome and Firefox have a very similar feature set most of the time now).
Just thought that I should add:
+1!
I'm a very old supporter of firefox but Opera has won me over for the past few years (currency conversion via text highlight, auto popup for ..., chrome/chromium base which allows extensions via Install Chrome Extensions)
.
{EDIT:} Just found the option for this in v102.0.1 (64-bit):
Menu -> Settings -> Privacy & Security -> Permissions -> Autoplay -> Settings -> Default For All Websites -> [XXXXX]