Gregory's Server
@dethos
Interestingly, the feature exists in non-advertised and less developed form in regular 114.2 (at least). There is a partial-duplicate article for it here: https://support.mozilla.org/en-US/kb/addons-restricted-domains
I had a look at my `extensions.webextensions.restrictedDomains`. To my surprise, it was populated with some additional domains - domains which, indeed, appear to point to banking websites. I tried resetting the setting, but it remained in its modified form. I deleted the content manually, and on pressing Enter all of the Mozilla restricted domains were left out, but the 'banking' domains remained.
After following the deactivation fix in the article, I tried resetting the setting again, and it went back to the normal list of Mozilla domains. So, I am mystified by this decision, and I hope they are doing it on sound grounds.
For reference, here is my list as it was:
autoatendimento.bb.com.br,ibpf.sicredi.com.br,ibpj.sicredi.com.br,internetbanking.caixa.gov.br,www.ib12.bradesco.com.br,www2.bancobrasil.com.br
@dethos Even more interesting. This request has been "in development" for some time, received comment from Mozilla employees (beyond the community manager), and has requests merged in which specifically mention this idea. It looks like Mozilla has been laying the technical groundwork, and now has the infrastructure to block specified extensions on specified sites with that warning. The caveat is that, in this early stage, all of the specification is done by them - the specified extensions are presumably just Mozilla-recommended/reviewed extensions, while the specified sites are (for some reason) opaque and seemingly arbitrary. Most odd, but hopefully to be better explained soon.
@dethos Even more interesting. This request has been "in development" for some time, received comment from Mozilla employees (beyond the community manager), and has requests merged in which specifically mention this idea. It looks like Mozilla has been laying the technical groundwork, and now has the infrastructure to block specified extensions on specified sites with that warning. The caveat is that, in this early stage, all of the specification is done by them - the specified extensions are presumably...