Open
Bug 1483599
Opened 6 years ago
Updated 2 years ago
Keyboard stops emitting repeats in a tree view in the Bootstrap code editor
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox63 | --- | affected |
People
(Reporter: MarcoZ, Unassigned)
References
()
Details
(Keywords: parity-chrome)
STR:
1. Visit http://www.bootstrapworld.org/preview/testing/space-invaders.html
2. Activate the Use Block Editor checkbox.
3. Shift-tab to the tree view.
4. If not on the first node, press Home.
5. Press Shift+LeftArrow to collapse all.
6. Hit and hold DownArrow to quickly scroll to the bottom.
Expected: If you continue to hold down the DownArrow key, you should land at the last node and hear error beeps as you cannot go any futther.
Actual: Scrolling stops some 20 or 30 items in, never reaches the bottom unless you release and press the key again.
This works fine in Chrome, Chrome never stops receiving the DownArrow and scrolls all the way to the bottom.
Reporter | ||
Updated•6 years ago
|
Summary: Keyyboard stops emitting repeats in a tree view in the Bootstrap code editor → Keyboard stops emitting repeats in a tree view in the Bootstrap code editor
Comment 1•6 years ago
|
||
P2 on the assumption that this is an important framework. Please downgrade to P3 if wrong.
Priority: -- → P2
Reporter | ||
Comment 2•6 years ago
|
||
Thanks, Henri! Yes, this is a tool currently in development which aims to help blind and visually impaired students learn programming more easily, by giving them an equivalent to syntax highlighting in code editors for sighted people. Chrome parity would be very good for Firefox growth and user retention. And studies show that this helps even more people than just blind and low-vision users.
Updated•6 years ago
|
Keywords: parity-chrome
Whiteboard: [parity-chrome]
Assignee | ||
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•