Closed Bug 907102 Opened 12 years ago Closed 10 years ago

[Messages] Focusing on the messages field is hard

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: janjongboom, Unassigned)

Details

Attachments

(2 files)

Attached video VID_20130820_110802.mp4
This is on 1.1 hamachi partner release from the beginning of August. The messages area in SMS is very hard to focus, I think I miss it about 70% of the time. Please see the video.
Summary: [SMS] Focusing on the messages field is hard → [Messages] Focusing on the messages field is hard
Yes, if you click on the right spot :p. The thing is that (at least for me) I tap right above the sweet spot and the thing will unfocus which happens a lot.
(In reply to Jan Jongboom [:janjongboom] from comment #2) > Yes, if you click on the right spot :p. The thing is that (at least for me) > I tap right above the sweet spot and the thing will unfocus which happens a > lot. But that's not a bug in Messages app
It is. The hit area is too small.
(In reply to Jan Jongboom [:janjongboom] from comment #4) > It is. The hit area is too small. The event is bound to the entire input element, not just a portion of it.
Attached image Element is very small
As you can see in this screenshot the element is only a small portion of the message area. User perception will be that all is clickable but thats not the case. Atm the height is 23px and the top and bottom aren't clickable (form has total height of 37px). That's way too small according to all UX guidelines out there (f.e. http://www.lukew.com/ff/entry.asp?1085). I'd suggest we even take the 20 pixels above this as hit area because there is nothing else that's interesting for the user there. If a click ends about somewhere around there it's probably for one of the controls in that bar.
I've just tried it myself, and I could focus on the text input field 2 out of 8 times I tapped into what I consider the SMS text field. Whatever issue it really is, the effect is that it is potentially really frustrating for the user IMHO.
I think this is valid, and we'd perfectly accept a patch about this :)
blocking-b2g: --- → koi?
this is not blocking for the v1.2 release but fixes definitely welcome. master is open now. will you be able to provide a patch?
blocking-b2g: koi? → ---
Flags: needinfo?(janjongboom)
I'm currently in the middle of Keyboard 1.2 work, but I can write a patch after that.
Flags: needinfo?(janjongboom)
Assignee: nobody → janjongboom
Might be automagically fixed by event fluffing in bug 900638 :) It's worth waiting for this.
Depends on: 900638
No, APZC is not being used in the messages app (at least not yet) so bug 900638 will not help you here.
kats> oki, thanks. And is it something possible in a soonish future, or should we try to use more traditional means for this specific bug (ie make the target bigger) ?
Event fluffing should already be happening in the messages app, AFAIK. So if it's not triggering easily either it's hitting an edge case in the fluffing code, or you just need to make the target bigger. Based on comment 6 it sounds like making it bigger would help regardless. I don't know the details of the fluffing algorithm so I don't know if it's likely that there is a bug in this case.
Yeh this should already be working on the messages app https://github.com/mozilla/mozilla-central/blob/master/layout/base/PositionedEventTargeting.cpp#L171 Vivien added which should mean contentEditable areas work and are targetted by fluffing, its pretty simple to check if fluffing it working (absolutely position a div where your click happens, click near
No longer depends on: 900638
Assignee: janjongboom → nobody
I think it works fine these days, at least nobody complained for a long time.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: