492409 - Spatial navigation with arrow keys breaks stuff on touch screen devices

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Al Billings [:abillings - ex-MoCo]]

If a user is on a web page that uses arrow keys for options (such as the search suggestons on http://www.google.com), using the arrow keys invokes the spacial navigation code for weird results.

Steps to Reproduce
1. Go to http://www.google.com
2. type "America" in the search box - suggested results should appear in an AJAXy fake drop down.
3. Use the down arrow to navigate down the list of suggestions

Result: Rendering goes very crazy as you navigate down the list.

Comment 1

[Ben Combee (:bcombee)]

We're probably going to disable spatial navigation for Fennec, as we're also seeing problems with apostrophe opening a quick find bar.

Comment 2

[Brian Crowder]

Spatial navigation strikes me as pretty critical, are we talking about ditching it forever?

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to comment #2)
> Spatial navigation strikes me as pretty critical, are we talking about ditching
> it forever?

No, not forever.

(In reply to comment #1)
> We're probably going to disable spatial navigation for Fennec, as we're also
> seeing problems with apostrophe opening a quick find bar.

We have a fix for the apostrophe (bug 471229)

Comment 4

[Antonio Gomes (tonikitoo)]

(In reply to comment #0)
> If a user is on a web page that uses arrow keys for options (such as the search
> suggestons on http://www.google.com), using the arrow keys invokes the spacial
> navigation code for weird results.
> 
> Steps to Reproduce
> 1. Go to http://www.google.com
> 2. type "America" in the search box - suggested results should appear in an
> AJAXy fake drop down.
> 3. Use the down arrow to navigate down the list of suggestions
> 
> Result: Rendering goes very crazy as you navigate down the list.

al billings, we have a bug on SNAV to not handle actions if current node has its own keypress handlers (which is pretty much the case of google suggestion, for example) - see bug 305657.

I will work on it now since bug 436084 (its blocker) is now fixed.

making it a dep bug 305657 (not to dup it).

please, if more stuff annoying you about SNAV, report it here and we can try using this bug as meta for snav.

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

vote for not blocking1.0

bug 305657 depends on bug 448602, which hasn't landed yet. let's disable SNAV for 1.0

Comment 6

[Mark Finkle (:mfinkle) (use needinfo?)]

We disabled SNAV for Fennec 1.0

Comment 7

[BMO Automation]

Closing all opened bug in a graveyard component