Closed
Bug 925307
Opened 11 years ago
Closed 11 years ago
[Contacts] In search mode, clicking ENTER on the keyboard exits the search mode
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(blocking-b2g:-, b2g-v1.2 fixed, b2g-v1.3 fixed)
People
(Reporter: gtorodelvalle, Assigned: gtorodelvalle)
References
Details
Attachments
(3 files)
432 bytes,
text/html
|
jmcf
:
review+
arcturus
:
approval-gaia-v1.2+
|
Details |
26.88 KB,
image/png
|
Details | |
432 bytes,
text/html
|
jmcf
:
review+
arcturus
:
approval-gaia-v1.2+
|
Details |
TO REPRODUCE: 1. Open the Contacts app. 2. Click on the search bar. The search mode opens. 3. Click on the INTRO key on the keyboard. EXPECTED RESULT: 4. The search mode is not exited. OBSERVED RESULT: 4. The search mode is exited and the Contacts app goes back to normal mode.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gtorodelvalle
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → koi?
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #815331 -
Flags: review?(jmcf)
Updated•11 years ago
|
Attachment #815331 -
Flags: review?(jmcf) → review+
Comment 2•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/7f240f2da3178b275315790585396629dbe2d756
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → 1.2 C2(Oct11)
Comment 3•11 years ago
|
||
ni? ayman to confirm the spec. this should be working as intended. may need to back out after Ayman confirms
Updated•11 years ago
|
Flags: needinfo?(aymanmaat)
Assignee | ||
Comment 4•11 years ago
|
||
In fact, this was the way it was implemented. The inclusion of the new HTML lazy loading functionality just make this stop functioning so somehow we introduced a regression this patch fixes ;-)
Comment 5•11 years ago
|
||
Hi, What exactly is the intro key? How does it impact the user if not fixed?
Flags: needinfo?(gtorodelvalle)
Assignee | ||
Comment 6•11 years ago
|
||
Hey! My bad, I meant the ENTER key (http://en.wikipedia.org/wiki/Enter_key). Regarding the user, the problem is that clicking on this key the search mode exits and the user comes back to the normal mode. The user may be tempted to click this return key until she notices that the search is made automatically as she types characters :-)
Flags: needinfo?(gtorodelvalle)
Comment 7•11 years ago
|
||
Comment 8•11 years ago
|
||
Plase see screenshot attached. Besides the Search mode is exited, the screen is not correctly shown.
Assignee | ||
Comment 9•11 years ago
|
||
Just tested it with Gecko-c4665b7 and latest Gaia from master (as for some minutes ago) and it is working fine ;-)
Assignee | ||
Comment 10•11 years ago
|
||
Waiting for Ayaman's feedback to request approval for v1.2 ;-)
Comment 11•11 years ago
|
||
(In reply to Joe Cheng [:jcheng] from comment #3) > ni? ayman to confirm the spec. this should be working as intended. may need > to back out after Ayman confirms Hey guys. As far as i am aware tapping on the INTRO (ENTER) key on the keyboard when the contacts list is in search mode and there is nothing in the search text input field should result in nothing happening. search mode should not be existed and the keyboard should not be closed... nothing should happen. The user should remain in search mode. The screenshot in comment 7 demonstrates incorrect behaviour. We have a dragdown action on the keyboard implemented that closes it.
Flags: needinfo?(aymanmaat)
Comment 12•11 years ago
|
||
(In reply to gtorodelvalle from comment #9) > Just tested it with Gecko-c4665b7 and latest Gaia from master (as for some > minutes ago) and it is working fine ;-) So this issue is not reproducible? Hi Ayman maat :maat What you are suggesting seems is that there is a fix for the dragdown action on keyboard? Is that an enhancement to 1.2?
Flags: needinfo?(aymanmaat)
Summary: [Contacts] In search mode, clicking INTRO on the keyboard exits the search mode → [Contacts] In search mode, clicking ENTER on the keyboard exits the search mode
Comment 13•11 years ago
|
||
(In reply to Preeti Raghunath(:Preeti) from comment #12) > (In reply to gtorodelvalle from comment #9) > > Just tested it with Gecko-c4665b7 and latest Gaia from master (as for some > > minutes ago) and it is working fine ;-) > > So this issue is not reproducible? > > Hi Ayman maat :maat > What you are suggesting seems is that there is a fix for the dragdown action > on keyboard? Is that an enhancement to 1.2? nop, i am not suggesting that. I was just observing that the is now the ability to drag down keyboard. I do not know if this is an enhancement to V1.2 because i have not been part of the team that introduced that action.
Flags: needinfo?(aymanmaat)
Comment 14•11 years ago
|
||
triage: should not block release. please ask for approval to land in v1.2. tks
blocking-b2g: koi? → -
Assignee | ||
Comment 15•11 years ago
|
||
My great contribution to Science for today :-) As suggested by Ayman, clicking on the ENTER key when in Search mode and the focus in on the search input text field does nothing: (1) it does NOT close the search mode and (2) it does NOT collapse the keyboard. As soon as I have José Manuel's r+, we'll merge this new patch and ask for v1.2 approval. Thanks!
Attachment #821704 -
Flags: review?(jmcf)
Assignee | ||
Comment 16•11 years ago
|
||
Since we were hiding the keyboard when clicking on the ENTER key and this was not the desired behavior ;-)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Attachment #821704 -
Flags: review?(jmcf) → review+
Comment 17•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/fa366f051e657d49406dfebc433ccd69ea62353d
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 18•11 years ago
|
||
Comment on attachment 815331 [details] 12771.html NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] [Bug caused by] (feature/regressing bug #): New lazy HTML loading mechanism [User impact] if declined: Bad experience (leaving the Search mode probably unexpectedly) [Testing completed]: On-device testing [Risk to taking this patch] (and alternatives if risky): Very low [String changes made]: None
Attachment #815331 -
Flags: approval-gaia-v1.2?
Assignee | ||
Comment 19•11 years ago
|
||
Comment on attachment 821704 [details] 13069.html NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] [Bug caused by] (feature/regressing bug #): New lazy HTML loading mechanism [User impact] if declined: Bad experience (leaving the Search mode probably unexpectedly) [Testing completed]: On-device testing [Risk to taking this patch] (and alternatives if risky): Very low [String changes made]: None
Attachment #821704 -
Flags: approval-gaia-v1.2?
Assignee | ||
Comment 20•11 years ago
|
||
PLEASE NOTICE THAT THIS PATCH IS COMPOSED OF 2 PULL REQUESTS AND CONSEQUENTLY OF 2 COMMITS ;-) Thanks!
status-b2g-v1.2:
--- → affected
Updated•11 years ago
|
Attachment #815331 -
Flags: approval-gaia-v1.2? → approval-gaia-v1.2?(francisco.jordano)
Updated•11 years ago
|
Attachment #821704 -
Flags: approval-gaia-v1.2? → approval-gaia-v1.2?(francisco.jordano)
Comment 21•11 years ago
|
||
Working correctly on master (10/29 build): Gecko-5fff789 Gaia-9fa7a86
Comment 22•11 years ago
|
||
Comment on attachment 815331 [details]
12771.html
moving code to the correct place, no risky.
a=me
Attachment #815331 -
Flags: approval-gaia-v1.2?(francisco.jordano) → approval-gaia-v1.2+
Comment 23•11 years ago
|
||
Comment on attachment 821704 [details]
13069.html
Follow up of the previous bug, also non risky
a=me
Attachment #821704 -
Flags: approval-gaia-v1.2?(francisco.jordano) → approval-gaia-v1.2+
Comment 24•11 years ago
|
||
Hi John, Could you please help us with the uplift to v1.2? thanks!
Flags: needinfo?(jhford)
Comment 25•11 years ago
|
||
There's a merge conflict: # both modified: apps/communications/contacts/js/views/search.js
Flags: needinfo?(jhford)
Assignee | ||
Comment 26•11 years ago
|
||
Hi John, I guess the problem was due to the fact that this bug included a couple of pull requests and consequently a couple of commits. I just ran: git checkout v1.2 git cherry-pick -x 0e085759b69f24ef9c8d1299ed1bd4d7a3268528 git cherry-pick -x bac2948c4ee6aecdd5d622f47866b9631acbd762 git push remote-mozilla-b2g-gaia v1.2 without problems. So I just merged them in v1.2: https://github.com/gtorodelvalle/gaia/commit/0e085759b69f24ef9c8d1299ed1bd4d7a3268528 -> https://github.com/gtorodelvalle/gaia/commit/bf77957071a61f3938d09e3147f88bf0a315a9f1 https://github.com/gtorodelvalle/gaia/commit/bac2948c4ee6aecdd5d622f47866b9631acbd762 -> https://github.com/gtorodelvalle/gaia/commit/d4d1709a7fdd376aa9390ad863e41569cbc59f91
Updated•11 years ago
|
status-b2g-v1.3:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•