611565 - form arrows are not intuitive

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Dietrich Ayala (:dietrich)]

after using fennec as the default browser for over a week, i just realized what those arrows are that were popping up at seemingly random times.

they're for moving around forms, right?

i think that because they're not visually tied to the element you're interacting with, i didn't put it together.

maybe a horizontal semi-transparent band that crosses the current form element. the band is touch sensitive, and dragging it up/down/across would select the next/previous field in tab order?

Comment 1

[Aakash Desai [:aakashd]]

Madhava, some love?

Comment 2

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

I don't expect we will change any of this for 4.0

Comment 3

[Dietrich Ayala (:dietrich)]

See also bug 611560, where I thought that the Form Helper was a rendering glitch.

The select list was showing at the bottom of the screen with a black background instead of inline, so I figured something was broken. Some border styling, and making the helper colors similar to the rest of Fennec's colors might help here.

Comment 4

[Dietrich Ayala (:dietrich)]

(In reply to comment #2)
> I don't expect we will change any of this for 4.0

Understandable. I'll stop filing bugs on it.

Comment 5

[Aakash Desai [:aakashd]]

I'd still like to see any new suggestions on how to improvement this feature at least get put into the discussion. Dietrich, can you offer a simple mock-up or, at least, a comparison of the type of behavior you'd prefer to see?

Comment 6

[Dietrich Ayala (:dietrich)]

I put a quick mockup of what i was thinking about in comment #0 here: http://imm.io/25Kp

Comment 7

[Dietrich Ayala (:dietrich)]

Probably could be done easily as an add-on, but I don't know how much like the cursor a single-touch is. Could you use regular drag/drop approach to move something around via touchscreen?

IIRC the new touch APIs aren't available on Android yet, but maybe they aren't necessary here.

Comment 8

[Aakash Desai [:aakashd]]

Madhava, ping?

Comment 9

[u88484]

(In reply to comment #5)
> I'd still like to see any new suggestions on how to improvement this feature
> at least get put into the discussion. Dietrich, can you offer a simple
> mock-up or, at least, a comparison of the type of behavior you'd prefer to
> see?
Google's stock browser on gingerbread places a next key at the end of the spacebar (makes the spacebar smaller to allow the next arrow to be drawn there).  I was just about to file a bug for that when I found this one.  Should I still create a new bug for that enhancement?

Comment 10

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

(In reply to comment #9)
> (In reply to comment #5)
> > I'd still like to see any new suggestions on how to improvement this feature
> > at least get put into the discussion. Dietrich, can you offer a simple
> > mock-up or, at least, a comparison of the type of behavior you'd prefer to
> > see?
> Google's stock browser on gingerbread places a next key at the end of the
> spacebar (makes the spacebar smaller to allow the next arrow to be drawn
> there).  I was just about to file a bug for that when I found this one. 
> Should I still create a new bug for that enhancement?

This belongs to bug 636339

Comment 11

[BMO Automation]

Closing all opened bug in a graveyard component