Revoking the permission to override keyboard shortcuts still lets thehill.com override page down behavior
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
Accessibility Severity | s3 |
People
(Reporter: erwinm, Unassigned)
References
()
Details
(Keywords: access, Whiteboard: [sci-exclude])
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Comment hidden (me-too) |
Updated•5 years ago
|
Comment 3•3 years ago
|
||
I have no idea how to do this when an editable element has focus because PageDown
is a navigation key, which may be managed by the native key bindings so that we cannot reserve the key simply...
https://searchfox.org/mozilla-central/rev/13d69189a8abfc5064fe44944550b9b6eb4544f5/dom/events/GlobalKeyListener.cpp#407-421
On the other hand, I don't know why it's not reserved in the other cases if user prevents web apps to override keyboard events. In my understanding, PageDown
key is managed by the GlobalKeyListener
...
Okay why do websites get to hijack navigation keys? Users may need to be able to navigate the websites without using mice.
Comment 5•3 years ago
|
||
(In reply to MarjaE from comment #4)
Okay why do websites get to hijack navigation keys?
Web apps can provide pseudo scrollable area, e.g., painting content into <canvas>
with self-rendered scrollbar. Therefore, from point of view of platform of web apps, any keyboard events should be exposed.
Comment 6•2 years ago
|
||
Triaging as access-s3 for now -- it sounds like the general issue here is around key hijacking, which is a separate issue from the motion sensitivity trigger of the particular page in #c0.
I'm going to See Also
our bug around creating a no-motion preference
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
•
|
||
I can't repro this bug using the original link [1], but a very similar or identical bug is easily repro'd at nationalzero.com, which uses disqus. To repro:
- Set permissions.defaults.shortcuts = 3 [ask] or 2 [deny].
- Open any article at nationalzero.com.
- Type ctrl/end. Notice how it properly displays the end of the article. Type ctrl/home and notice how it properly displays the top of the article.
- Scroll down to the comments.
- Scroll down until you see "Load more comments".
- Click it.
- Now type ctrl/home. Nothing happens. It should display the top of the article.
- Type ctrl/end. Nothing happens. It should display the bottom of the article.
See also bug 1795555.
[1] Maybe thehill.com fixed their override? I used to see the exact same bug there.
Description
•