-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Firefox support #40
Comments
Yes, it's still necessary. Unless the situation has changed, Firefox's To quote the README:
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 You can access that setting via |
@uBlock-user: I know about that switch in Btw., this switch disables auto play on ALL websites, if I need to enable auto play temporary I need to switch it to |
@Piter432 i think you can do this with uMatrix |
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. |
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. |
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 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. |
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: |
Like in title. Of course, if it's necessary
The text was updated successfully, but these errors were encountered: