Open
Bug 305657
Opened 19 years ago
Updated 2 years ago
Make Spatial Navigation not listen to key press handlers if page has its own handlers
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
NEW
People
(Reporter: dougt, Unassigned)
References
Details
When a page has key press handlers, spatial navigation shouldn't be listen to them.
Comment 1•17 years ago
|
||
This sounds like something that would need hooks into DOM events code; cc'ing smaug.
Updated•16 years ago
|
Assignee: nobody → tonikitoo
Component: XPCOM → Keyboard: Navigation
OS: Windows XP → All
Summary: Spatial Navigation → Make Spatial Navigation not listen to key press handlers if page has its own handlers
Comment 3•16 years ago
|
||
taking the bug. microb provides something close to this, lets try to adapt the solution
Status: NEW → ASSIGNED
QA Contact: xpcom → keyboard.navigation
Comment 4•16 years ago
|
||
(In reply to comment #3) > microb provides something close to this, lets try to adapt the solution hum, what microb actually does it to provide a black-list of sites where snav should be disable, because there known issues, or anything else ... so doug, would it still be desired to have in new snav implementation ? (in js)
Comment 5•16 years ago
|
||
Bug 448602 could be used to check if there are JS listeners for untrusted keypress events. That would be probably a bit slow if the whole DOM must be traversed - but I don't know any better way. We don't have any flags or anything which could tell if the page has key event listeners.
Assignee | ||
Updated•5 years ago
|
Component: Keyboard: Navigation → User events and focus handling
Comment 6•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: tonikitoo → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•