"#Google is now banning the popular Linux browsers named Konqueror, Falkon, and Qutebrowser from logging into Google services because they may not be secure." 🤦♂️
@Kevin And I'm seeing more sites that push you to use only chrome for transactions on that site. Shades of Microsoft IE a decade or so back. Ugh.
This is funny because I consider JS to be a security hole. (Yes there's a sandbox, no I don't trust it)
@Kevin Solution: don't use Google services. I never used Chrome anyway, very glad I never fell for it. It's pure evil, 100% malware. The web was more inclusive in IE6 days! Block Google to your sites! The Linux community is still way too friendly for Google/Android.
@Kevin That is dumb.
The best part is that you could just fake your browser info with a plugin an pass the check.
Google trying to call out others for not being secure. Funny. Luckily I don't use Google services so they can take their banning and shove it.
@Kevin NOOOO! my precious Falkon! They can't ban Falkon, I hate it slightly less than every other browser I've tried!
@Kevin "May not be secure", as opposed to Chrome that they made sure is not secure and will spy on you?
If you own a browser and you start to block other browsers you should get with an anti-trust lawsuit right in the face, at the bare minimum.
Please don't ask for my user agent string. Some of my answers may make you feel insecure.
Inhale, exhale, it's just that I don't need you.
@jookia @grainloom @Kevin I haven't implemented the input side yet, but you'd need to frame it in terms of hyperlinks. Those'll become commands the user can trigger either typing or speaking them aloud, as indicated by a preceding beep. Otherwise the page will be entirely static.
For the dropdown menu case you could link to a "#id" and tell it to only read the menu when it's the ":target". Or you could use <details> which'll do the exact same thing.