Closed
Bug 957714
Opened 11 years ago
Closed 11 years ago
[Messages] Interacting with message field prevents recipients field from stealing focus (cursor jump)
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(blocking-b2g:1.3+, b2g18 unaffected, b2g-v1.2 affected, b2g-v1.3 fixed)
Tracking | Status | |
---|---|---|
b2g18 | --- | unaffected |
b2g-v1.2 | --- | affected |
b2g-v1.3 | --- | fixed |
People
(Reporter: nkhristoforov, Assigned: rwaldron)
References
()
Details
(Keywords: regression, Whiteboard: dogfood1.3)
Attachments
(2 files)
When the user selects the Message text field, the typing cursor appears in the Message text field for a split-second then returns back to To: text field. The issue only occurs when the To: text field has an incorrect contact in it and the incorrect contact is selected. Having an existing contact or a number does not reproduce the issue.
Repro Steps:
1) Updated Buri to BuildID: 20140106004001
2) Open the Messaging app.
3) Select the New Message icon.
4) Select the To: field and input random letters so it does not have an existing contact.
5) Select the Message text field.
6) Select the contact with the red box around it then select the Message field again.
Actual:
The typing cursor will switch back to the To: field after steps 5 and 6.
Expected:
The typing cursor would remain in the Message text field.
Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140106004001
Gaia: 35a60b82f8cf2d759939a350e2dadbb9d8b2f5dc
Gecko: a43cb4b322d3
Version: 28.0a2
Firmware Version: V1.2_20131115
Repro frequency: 100%
See attached: Logcat and Video
Reporter | ||
Comment 1•11 years ago
|
||
URL for youtube video: http://youtu.be/U_RAZh9WKYk
This issue reproduces on 1.2 but does not reproduce on 1.1. On 1.1 the typing cursor stays on the Message text field.
Device: Buri 1.1 COM
BuildID: 20140102041202
Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f
Gecko: bdac595a4e46
Version: 18.0
RIL Version: 01.01.00.019.281
Firmware Version: V1.2_20131115
Device: Buri 1.2 COM
BuildID: 20140106004001
Gaia: 8441587c3b352e052fee07665c21fd192540f19f
Gecko: d552c08a72d0
Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version: V1.2_20131115
status-b2g18:
--- → unaffected
status-b2g-v1.2:
--- → affected
status-b2g-v1.3:
--- → affected
Keywords: regression,
regressionwindow-wanted
Assignee | ||
Comment 2•11 years ago
|
||
(In reply to Nikolai Khristoforov from comment #0)
> Created attachment 8357277 [details]
> Logcat
>
> When the user selects the Message text field, the typing cursor appears in
> the Message text field for a split-second then returns back to To: text
> field. The issue only occurs when the To: text field has an incorrect
> contact in it and the incorrect contact is selected. Having an existing
> contact or a number does not reproduce the issue.
>
> Repro Steps:
> 1) Updated Buri to BuildID: 20140106004001
> 2) Open the Messaging app.
> 3) Select the New Message icon.
> 4) Select the To: field and input random letters so it does not have an
> existing contact.
> 5) Select the Message text field.
> 6) Select the contact with the red box around it then select the Message
> field again.
>
> Actual:
> The typing cursor will switch back to the To: field after steps 5 and 6.
IIRC, this is intentional because the contact is invalid. I'll have to go back and review all of the discussion for this feature to confirm.
Comment 3•11 years ago
|
||
Can UX weigh in on what the correct behavior is here with a rationale why?
Flags: needinfo?(firefoxos-ux-bugzilla)
Keywords: regressionwindow-wanted
Assignee | ||
Comment 4•11 years ago
|
||
Another aspect to consider is that the user wouldn't be able to send a message to a single invalid recipient: the send button is disabled until there is a valid recipient, whether that's a known contact or the number of an unknown contact.
Comment 5•11 years ago
|
||
I actually think this is an unwanted behavior.
I think the "focus in the To: field" behavior happens because we're "assimilating" the recipient, and probably the invalid case has not the same path than the valid case.
If the user taps the "messages" field, then we should focus it, and not focus back to the recipients panel, even if it's invalid.
I ask 1.3? blocking for regression from 1.1.
Asking needinfo from Ayman directly as well.
blocking-b2g: --- → 1.3?
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(aymanmaat)
Assignee | ||
Comment 6•11 years ago
|
||
I agree that it's strange, and I'm going to take this for now so that I can start poking around the code to see what I can come up with. I'm confident that this is caused by the async nature of recipient validation.
Updated•11 years ago
|
Keywords: regressionwindow-wanted
Comment 7•11 years ago
|
||
This is probably a regression from bug 920546.
Updated•11 years ago
|
Keywords: regressionwindow-wanted
Assignee | ||
Comment 8•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #7)
> This is probably a regression from bug 920546.
Not probably, it absolutely is, but I don't yet know how to work around it in a reasonably elegant way.
Comment 9•11 years ago
|
||
as stated in comment 7 and comment 8 this is a regression so i support moving this to 1.3+ in triage.
I also agree with Julien's comment 5 that the behaviour described in comment 0 is unwanted behaviour. Therefore if the user focuses the 'message field' we should focus on it regardless of the content of the 'to field'
Flags: needinfo?(aymanmaat)
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Comment 10•11 years ago
|
||
since we need to close 1.3 bugs by the end of Jan, assign to Rick for now. Please feel free to unassign if you are not working on it. thanks
Assignee: nobody → waldron.rick
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to Joe Cheng [:jcheng] from comment #10)
> since we need to close 1.3 bugs by the end of Jan, assign to Rick for now.
> Please feel free to unassign if you are not working on it. thanks
I've been actively working on this—it's not a simple issue with a simple fix.
Comment 12•11 years ago
|
||
Thanks Rick
since 1.3+ is the highest priority now, set target milestone, please make the change if it doesn't work. thanks
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
Comment 13•11 years ago
|
||
Hey Rick, this should land as soon as possible now. Do you think you'll be able to have a first patch soon? Would you prefer that someone (maybe me :) ) take this over?
Assignee | ||
Updated•11 years ago
|
Summary: [B2G][SMS] Typing cursor switches back to To: text field after user select Message text field → [Messages] Typing cursor switches back to To: text field after user select Message text field
Assignee | ||
Updated•11 years ago
|
Summary: [Messages] Typing cursor switches back to To: text field after user select Message text field → [Messages] Interacting with message field prevents recipients field from stealing focus (cursor jump)
Assignee | ||
Comment 14•11 years ago
|
||
I've manually tested as many user typing scenarios I could come up with, but another rigorous look would be ideal.
Attachment #8366691 -
Flags: review?(felash)
Comment 15•11 years ago
|
||
Comment on attachment 8366691 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/15770
r=me with a little nit
Attachment #8366691 -
Flags: review?(felash) → review+
Assignee | ||
Comment 16•11 years ago
|
||
Comment on attachment 8366691 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/15770
I've addressed the weird behaviour, so I'm effectively turning down the "r+" :)
Attachment #8366691 -
Flags: review+ → review?(felash)
Comment 17•11 years ago
|
||
Comment on attachment 8366691 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/15770
r=me
LET'S LAND THIS ;)
Attachment #8366691 -
Flags: review?(felash) → review+
Assignee | ||
Comment 18•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 19•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•