I don't know that uMatrix will be supported any time soon, but you can turn uBlock Origin into Advanced mode and get much of the same functionality that way.
They're not killing it. Preview/Fenix is essentially a complete re-write of the mobile browser, and they just haven't added all of the extension hooks back into the new version yet.
I think the metrics actually show that most users don't use extensions. But of the group that do use extensions, I'd guess an adblocker is the top one.
The question is - _an_ adblocker or _the_ adblocker (ublock)? As a long time FF Android user I prefer uMatrix and will wait with upgrade, hoping they fix this quickly. Otherwise... Not sure what I'll do. This is bad. :-(
As far as I know, uMatrix is not a (dynamic) ad blocker. That is, if some requests to subdomain.domain.net are for ads and some of the requests are for important page content, uMatrix isn't capable of distinguishing between the two. A real ad blocker uses block lists compiled (at least in part) by other people that can distinguish between two different URLs on the same domain.
Fair point, except - I am more concerned with tracking than the ads themselves. Which means I want to block Google fonts anywhere, and only allow domains when I want to. So no, I prefer uMatrix approach.
Isn't that what the following portion of the blog post is all about?
"As plugins today, the CDM itself will be distributed by Adobe and will not be included in Firefox. The browser will download the CDM from Adobe and activate it based on user consent."
Though many of them can if you use something like this to dig into the browser internals:
var {Cc, Ci} = require("chrome");
Then just use "Cc" instead of "Components.classes" and "Ci" instead of "Components.interfaces" for anything that needs them.
For example, the code in the "adding a stylesheet" section of this page ( https://developer.mozilla.org/en/Using_the_Stylesheet_Servic... ) would look like this:
var sss = Cc["@mozilla.org/content/style-sheet-service;1"]
.getService(Ci.nsIStyleSheetService);
var ios = Cc["@mozilla.org/network/io-service;1"]
.getService(Ci.nsIIOService);
var uri = ios.newURI("chrome://myext/content/myext.css", null, null);
sss.loadAndRegisterSheet(uri, sss.USER_SHEET);
(Assuming you actually have a stylesheet registered at "chrome://myext/content/myext.css", you will just have registered it with the stylesheet service, and it will take effect immediately.)
"rust-acean"