<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>49068</bug_id>
          
          <creation_ts>2010-11-05 07:07:02 -0700</creation_ts>
          <short_desc>Spatial Navigation: Support &lt;input type=text&gt; with JS handlers attached to it.</short_desc>
          <delta_ts>2013-07-30 05:24:05 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Accessibility</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>PC</rep_platform>
          <op_sys>OS X 10.5</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>46905</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Antonio Gomes">tonikitoo</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>skyul</cc>
    
    <cc>yiyuanhust</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>305256</commentid>
    <comment_count>0</comment_count>
    <who name="Antonio Gomes">tonikitoo</who>
    <bug_when>2010-11-05 07:07:02 -0700</bug_when>
    <thetext>If the &lt;input type=text&gt; 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&apos;s main search input field.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>328085</commentid>
    <comment_count>1</comment_count>
    <who name="yiyuan">yiyuanhust</who>
    <bug_when>2010-12-30 18:29:23 -0800</bug_when>
    <thetext>(In reply to comment #0)
&gt; If the &lt;input type=text&gt; has JS handlers attached to it handling arrow keys, spatial navigation does not work.
&gt; 
&gt; e.g.: with spatial navigation ON, try moving the focus up (or down in google.com&apos;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 &quot;EditorClient ::handleKeyboardEvent&quot;,  just return while spatial navigation is on, and key event is  up(or down ,left, right)  !</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>912669</commentid>
    <comment_count>2</comment_count>
    <who name="Kwang Yul Seo">skyul</who>
    <bug_when>2013-07-29 22:13:50 -0700</bug_when>
    <thetext>(In reply to comment #0)
&gt; If the &lt;input type=text&gt; has JS handlers attached to it handling arrow keys, spatial navigation does not work.
&gt; 
&gt; e.g.: with spatial navigation ON, try moving the focus up (or down in google.com&apos;s main search input field.

I tried to reproduce the bug in r153457 (WK2 GTK+), but confirmed that the bug had been fixed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>912787</commentid>
    <comment_count>3</comment_count>
    <who name="Antonio Gomes">tonikitoo</who>
    <bug_when>2013-07-30 05:24:05 -0700</bug_when>
    <thetext>(In reply to comment #2)
&gt; (In reply to comment #0)
&gt; &gt; If the &lt;input type=text&gt; has JS handlers attached to it handling arrow keys, spatial navigation does not work.
&gt; &gt; 
&gt; &gt; e.g.: with spatial navigation ON, try moving the focus up (or down in google.com&apos;s main search input field.
&gt; 
&gt; 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.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>