2. It seems a bit weird to be concerned about UI patterns if you earnestly want this component to do its job.
3. If it's that important, the Escape key event can be added after DOMContentLoaded. Warn content authors to not overuse the component, and it would be fine. You can still have the triple-Shift key event for those cases that they specifically call out.
- they don’t have a smartphone, or it’s been taken off them
- they’re forced to use a desktop because their abuser doesn’t want them to do things in private easily
- plausibly mobile has something different entirely, given that this appears to be desktop focused.
- They mention escape is intercepted by most browsers to stop loading, if someone is interrupted midway and panics and starts hitting escape, they could plausibly end up _stuck_ on the page they were trying to hide from their abuser.
2. I don't understand this comment. Surely this is a perfect example of when you want a component to work as well as possible, including UI research?
3. The mAjor point here is that the functionality of the escape key is ambiguous. It can do various things in various contexts, so you can't rely on people to use it for that, and visitors can't rely on it because it might just e.g. minimise a maximised window on MacOS, leaving the website on-screen.