845667 - [ SMS ] Once contact is fetched from address book the cursor position is not showing in Message field

Status: RESOLVED FIXED

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

Description

[Leo]

1. Title : Once contact is fetched from address book the cursor position is not showing in Message field
2. Precondition : Contacts should exists in contacts app.Composing of a new message should be possible
3. Tester's Action : Messaging - New message - Select contact from list
4. Detailed Symptom (ENG.) :Once the contact is selected from contact picker in compose message screen,the cursor is not moving to Message field automatically
5. Expected : The cursor position should be shown in Message field once contact is fetched.
6.Reproducibility: Y
1)Frequency Rate : 100%
7.Gaia Revision: 6916e18d1f72936e892543cf4a104a7d457f78ad

Comment 1

[Leo]

Attachment: Pointer to pull request

Comment 2

[Borja Salguero [:borjasalguero]]

Hi Leo,
'Focus' behaviour was fixed long time ago following UX specs, so this modifications should be reviewed first if it's a bug or not. Could you clarify with UX Team? Thanks!

Comment 3

[Leo]

Hi,

Thanks for the reply. Will you please share a UI spec, which explains about the "Focus" behavior? This will really help me to understand it and then contact UX team.

Also please let me know the person to whom I should be contacting for UX confirmation.

Comment 4

[Borja Salguero [:borjasalguero]]

Hi Leo,
I tried to attach the old Wireframe, but the link it's not working... :S. https://wiki.mozilla.org/Gaia/SMS The 'interaction' section it's not working at all. However the 'focus' was fixed and agreed during Berlin Working Week, and it's the currently implemented one, so I think there is no bug here.

Comment 5

[bhavana bajaj [:bajaj]]

Not blocking based on comment# 4 and looks more like a convenience factor,would not block on this.

Comment 6

[Borja Salguero [:borjasalguero]]

This one was fixed with the new implementation of the sms-layout https://github.com/mozilla-b2g/gaia/commit/482008ef3e9501afea1580dc7c1094333622eb83 . Please close the PR tied to this bug. Thanks!