This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Most banking apps don’t work on rooted Android phones. It’s not the same, but I don’t think it’s a stretch to assume that at least these companies would force their customers to use specific software…
And I use my root to hide my root from my banking app… Idk about the implementation details of this, but I kinda think the same could happen here as well.
This is the problem for me. If my bank or other critical institution decides to refuse me access with Firefox, I can’t use Firefox. This is the crux of the issue. Chrome is creating a browser monopoly with it’s market dominance and attestation scheme.
MS tried to exert control in the early 2000s with its IE dominance and was thwarted by an anti-trust lawsuit. Google will probably skate on this one. Nowadays the consumer is only a resource to be plundered. The customer is shit.
May be a bit problematic with banks, insurances and maybe government institutions…
it will truly be messed up if essential websites block user access because of this
Most banking apps don’t work on rooted Android phones. It’s not the same, but I don’t think it’s a stretch to assume that at least these companies would force their customers to use specific software…
And I use my root to hide my root from my banking app… Idk about the implementation details of this, but I kinda think the same could happen here as well.
This is the problem for me. If my bank or other critical institution decides to refuse me access with Firefox, I can’t use Firefox. This is the crux of the issue. Chrome is creating a browser monopoly with it’s market dominance and attestation scheme.
MS tried to exert control in the early 2000s with its IE dominance and was thwarted by an anti-trust lawsuit. Google will probably skate on this one. Nowadays the consumer is only a resource to be plundered. The customer is shit.