Summary: | Spatial Navigation and caret browsing do not work well together | ||
---|---|---|---|
Product: | WebKit | Reporter: | Yael <yael> |
Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | gustavo, jdiggs, joone, mburtin, mrobinson, tonikitoo, xan.lopez |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 50536 | ||
Bug Blocks: |
Description
Yael
2010-10-06 09:04:49 PDT
Gustavo, who is using caret browser on your side? I believe Xan would know about this. We use caret browsing in Epiphany, as an accessibility feature, for instance. joanmarie, you might also be interested here. (In reply to comment #0) > Both Spatila Navigation and caret browsing want to consume the key events. > Seems to me that we should restrict use of one or the other, but not both. My understanding is that it does not make sense/it's impossible to have both enabled at the same time, so I agree we should probably not allow it. (In reply to comment #1) > Gustavo, who is using caret browser on your side? Sorry that I'm a tad late to this game. But to re-iterate what others have been saying: Caret navigation is needed for accessibility, including for users who are blind who are arrowing within the content and having it presented to them via tts and/or refreshable braille. Having both enabled at the same time does seems like a problem. ;-) |