3 ms·
People don't read buttons. However, I share your disdain for Chrome's chosen method; it's very gate-keepery. It requires you to be "in the know"; those who
by wearywanderer 5y ago
People don't read buttons. However, I share your disdain for Chrome's chosen method; it's very gate-keepery. It requires you to be "in the know"; those who understand the danger but haven't heard of the trick are deliberately left out.
I think a reasonable compromise would be a button that pulls up a dialog prompting you to type out a consent message. The dialog tells you what to write instead of keeping this as esoteric knowledge, but the user is still compelled to at least read the warning instead of blindly pressing buttons.
- bawolff 5y agoCompare to firefox which has no bypass. This is the sort of thing, if you're not in the know than you probably dont understand the consequences.
- wearywanderer 5y ago> This is the sort of thing, if you're not in the know than you probably dont understand the consequences. Understanding the premise and importance of HTTPS and knowing about some esoteric hidden UX of some Google software are not at all the same thing.