Closed Bug 833552 Opened 12 years ago Closed 12 years ago

Tapping "+" on Compose Screen Briefly Shows Keyboard

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

x86
macOS
defect
Not set
normal

Tracking

(b2g18 fixed)

RESOLVED FIXED
Tracking Status
b2g18 --- fixed

People

(Reporter: davidwalsh, Assigned: kgrandon)

Details

Attachments

(1 file)

Tapping the "+" text in the "to" line of new email composition briefly shows the keyboard before bringing up the contact screen; we should avoid showing the keyboard at all.
This is a sort-of expected outcome from the landing of bug 812534 in which we greatly enlarged the region where clicking will focus the input box. What will happen now is we will trigger the contact-picker activity, but then the 'click' event will also bubble to focus the input. Probably the best/easiest solution is to have onContactAdd call stopPropagation() and then *maybe* force the input field to be focused when we return. The keyboard showing up can be fairly annoying, so we might be better off not triggering the keyboard at all... Casey, what should we do? Also, can we get that codified into the interaction diagrams since focus has turned out to be a pretty important thing for these fields?
Flags: needinfo?(kyee)
I know it's usually easier said than done but: Could we not have it so that the To input field doesn't overlap the "+"? This way the user wouldn't inadvertently focus the input field causing the keyboard to pop-up? Ideally we also have the subject field focused with the keyboard up when you return back so you can directly start entering a subject. Agree on adding this to the IxD. I will work on doing that.
Flags: needinfo?(kyee)
The input field doesn't overlap the "+". We added a "click" listener to a div that contains most of the line to transfer focus to that input, so it's a question of how the DOM is arranged and how we want the clicks caught. Click-wise, I presume we probably want a clear horizontal split. DOM-wise, I think we were trying to avoid causing visual regressions, and I think we would stick with that on any branches where we are supposed to be conservative with changes.
Oops, looks like I definitely caused this one! Would tend to agree with Andrew that the best fix for now would be stopPropagation(). I think auto-focusing the subject line might cause usability issues when trying to send a mail to more than one recipient. That should probably be tracked in a different bug. Andrew - Being this bug's father, I will assign to myself and create a pull request for you to review. Unless you really want to take it?
Assignee: nobody → kgrandon
Simple polish change which makes it so the keyboard does not show when we add a contact to email. Also requesting approval for v1 so we can land on v1-train. Thanks!
Attachment #705158 - Flags: review?(bugmail)
Attachment #705158 - Flags: approval-gaia-v1?(21)
Attachment #705158 - Flags: review?(bugmail) → review+
This is now landed in master, thanks for the quick review. If we get v1 approval I'll cherry-pick it into v1-train. https://github.com/mozilla-b2g/gaia/commit/28944fcd761bf54a296d1da3f54f49cab87de00d
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment on attachment 705158 [details] Github pull request pointer approved for the v1-train, i.e. for the v1.0.1 release.
Attachment #705158 - Flags: approval-gaia-v1?(21) → approval-gaia-v1+
(In reply to Kevin Grandon from comment #7) > If we get v1 approval I'll cherry-pick it into v1-train. Beat you to it :) v1-train: 1b16d870660dd6cb0388679cd93c1438672f2bed
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: