Bug 47271 - Spatial Navigation and caret browsing do not work well together
Summary: Spatial Navigation and caret browsing do not work well together
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 50536
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-06 09:04 PDT by Yael
Modified: 2012-05-01 07:30 PDT (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yael 2010-10-06 09:04:49 PDT
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.
Comment 1 Antonio Gomes 2010-10-06 09:07:56 PDT
Gustavo, who is using caret browser on your side?
Comment 2 Gustavo Noronha (kov) 2010-10-06 12:12:32 PDT
I believe Xan would know about this. We use caret browsing in Epiphany, as an accessibility feature, for instance.
Comment 3 Antonio Gomes 2010-10-07 11:15:45 PDT
joanmarie, you might also be interested here.
Comment 4 Xan Lopez 2010-10-29 23:23:01 PDT
(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.
Comment 5 Joanmarie Diggs (irc: joanie) 2010-11-10 12:41:42 PST
(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. ;-)