Bug 49068 - Spatial Navigation: Support <input type=text> with JS handlers attached to it.
Summary: Spatial Navigation: Support <input type=text> with JS handlers attached to it.
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 46905
  Show dependency treegraph
 
Reported: 2010-11-05 07:07 PDT by Antonio Gomes
Modified: 2013-07-30 05:24 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Gomes 2010-11-05 07:07:02 PDT
If the <input type=text> has JS handlers attached to it handling arrow keys, spatial navigation does not work.

e.g.: with spatial navigation ON, try moving the focus up (or down in google.com's main search input field.
Comment 1 yiyuan 2010-12-30 18:29:23 PST
(In reply to comment #0)
> If the <input type=text> has JS handlers attached to it handling arrow keys, spatial navigation does not work.
> 
> e.g.: with spatial navigation ON, try moving the focus up (or down in google.com's main search input field.

the key event up(or down, left, right) use for move cursor between input string while focus on input text node . 

if you want spatial navigation work well while focus in Input Text node, you can change "EditorClient ::handleKeyboardEvent",  just return while spatial navigation is on, and key event is  up(or down ,left, right)  !
Comment 2 Kwang Yul Seo 2013-07-29 22:13:50 PDT
(In reply to comment #0)
> If the <input type=text> has JS handlers attached to it handling arrow keys, spatial navigation does not work.
> 
> e.g.: with spatial navigation ON, try moving the focus up (or down in google.com's main search input field.

I tried to reproduce the bug in r153457 (WK2 GTK+), but confirmed that the bug had been fixed.
Comment 3 Antonio Gomes 2013-07-30 05:24:05 PDT
(In reply to comment #2)
> (In reply to comment #0)
> > If the <input type=text> has JS handlers attached to it handling arrow keys, spatial navigation does not work.
> > 
> > e.g.: with spatial navigation ON, try moving the focus up (or down in google.com's main search input field.
> 
> I tried to reproduce the bug in r153457 (WK2 GTK+), but confirmed that the bug had been fixed.

Google site has changed. I will try to come up with a reduction.