zlacker

Browser detection. "Environment" detection.

How to design a website that is not accesible with Chrome. As a means of protest by certain website operators.

Would be fun to watch Google circumvent that. Especially if it was only popular amongst small, noncommercial websites.

>>1vuio0+(OP)
I like this idea. Help users by training them to use multiple browsers regularly. My kids already use multiple browsers (e.g. to block youtube ads on their android devices). People will happily use other browsers if they have a good reason to.

But rather than block them outright, I would disable all but the necessarily features snd keep reminding those users to either switch to another browser or to use something like tampermonkey (with clear instructions in what it needs to do).

What would be a good way to detect support for this stuff? The js api?

>>1vuio0+(OP)
This might be inspirational: >>25240299

>>1vuio0+(OP)
For a long 6 years, Chrome could not access my website (but all other web browsers can) because it was unable to respect server-side mandatory negotiation of non-HTTP/3 along with only ChaCha/Poly (no AES/RSA). Microsoft Edge fixed theirs shortly afterward.

Happy to say, Google just fixed it (about 4 months ago).

Many free cross-browser testing tools still can demonstrate the breakage (via version testing).