If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

form arrows are not intuitive

NEW
Unassigned

Status

Fennec Graveyard
General
7 years ago
7 years ago

People

(Reporter: dietrich, Unassigned)

Tracking

({ux-userfeedback})

Trunk
x86
Linux
ux-userfeedback

Details

(Reporter)

Description

7 years ago
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?
Madhava, some love?
Keywords: ux-feedback
I don't expect we will change any of this for 4.0
(Reporter)

Comment 3

7 years ago
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.
(Reporter)

Comment 4

7 years ago
(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.
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?
(Reporter)

Comment 6

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

Comment 7

7 years ago
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.
Madhava, ping?

Comment 9

7 years ago
(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?
(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
You need to log in before you can comment on or make changes to this bug.