Bug 49068
| Summary: | Spatial Navigation: Support <input type=text> with JS handlers attached to it. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Antonio Gomes <tonikitoo> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | skyul, yiyuanhust |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
| Bug Depends on: | |||
| Bug Blocks: | 46905 | ||
Antonio Gomes
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
yiyuan
(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) !
Kwang Yul Seo
(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.
Antonio Gomes
(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.