Closed
Bug 905458
Opened 11 years ago
Closed 7 years ago
[B2G][Gaia][e.me] [homescreen] [dialer] e.me search does not appear preserved during a call
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(b2g-v1.3T affected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-v1.3T | --- | affected |
People
(Reporter: jhammink, Unassigned)
Details
(Whiteboard: 1.3tarakorun2)
Attachments
(1 file)
15.74 KB,
image/png
|
Details |
STR
1) Tap Search Bar
2) Do a basic search
3) while it's searching, call into the device
4) Accept the incoming call, but hit the home button and go back to e.me
Actual:
e.me appears blank - as though nothing has been previously entered to search bar. Tapping the search bar again shows the text (and autosuggestions, apps) based on what was previously entered.
Expected:
e.me search bar, autosuggestion and screen already appears populated with the info previously entered to it. I should not need to tap the search bar explicitly to show this.
Helix version info
Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/afd50da34b9f
Gaia 4788826c0cfc7ca00dec36ed8dc6b3eaee9ec571
BuildID 20130813042203
Version 18.0
Leo Version info
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/15813d776a69
Gaia dd3959fa74e356a528daa76ffee14c2c728a4b56
BuildID 20130814041202
Version 18.0
Updated•11 years ago
|
blocking-b2g: --- → hd?
Updated•11 years ago
|
blocking-b2g: hd? → hd+
Flags: needinfo?(21)
Updated•11 years ago
|
Assignee: nobody → ran
Flags: needinfo?(21) → needinfo?(ran)
Hey John, can you try again please? I find that this works fine. try not to hit the home button to get to teh search result.
Gaia 1e9470b9b6df630eddf1c4c8b25b3170ee786b0e
SourceStamp 48faa2668dd8
BuildID 20130929004004
Version 26.0a2
helix
Flags: needinfo?(jhammink)
Reporter | ||
Comment 3•11 years ago
|
||
I'm not sure how I'm supposed to get back to the search after I answer an active call, without hitting the "home" button
Tested, via my original steps, on Helix nad I'm still seeing the same - or similar issue.
Gaia 51f3c79ea93bb91d3b12e50b49d203a049a94a9b
SourceStamp 3f16dc100b1f
BuildID 20131010004001
Version 26.0a2
It's unclear how this is supposed to work - but here's the flow I am seeing.
1.) Start a search from e.me search field. While it's in progress, call into the helix and answer the call on the helix.
2.) Tap the home button to get back to the search.
NOTE: e.me search field is now blank, (call in progress is shown at top of screen - see screenshot)
3.) tap the e.me search field again
NOTE: it's quirky and inconsistent, but usually on first tap, e.me brings up default icons and empty search.
4.) tap e.me search field again
NOTE: goes to call dialog with call in progress.
Sorry, I misunderstood the situation. If I understand things correctly now, you're going into home after receiving the call; but still on the call.
So what's occurring is the home is clearing the search. ( bug 922411 )
It's possible that bug 922411 might not get fixed, but this one should IMO. Thanks for clarifying.
Comment 5•11 years ago
|
||
Ok guys, thanks for the feedback.
It's never been brought to our attention. We'll see what we can do.
Flags: needinfo?(ran)
Comment 6•11 years ago
|
||
Actually, this is not an e.me issue.
Only in this scenario does the homescreen get the "Home button" clicked event - even though it shouldn't.
Here's another scenario in which this happens (unrelated to e.me)
STR:
1. In the homescreen, move to 2nd page.
2. Get call and click home button.
3. The 2nd page is shown and immediately the user is taken to the homescreen.
Cristian, can you assist in understanding this?
Flags: needinfo?(crdlc)
Comment 7•11 years ago
|
||
Removing blocker on this given the use case and low impact when occurs, spending more time on investigation.
blocking-b2g: hd+ → ---
Comment 8•11 years ago
|
||
IMHO your steps are ok and I will expect that behavior, right? or do you mean that we go to landing page? I think that you have to investigate why the field doesn't show the text. Maybe, we shouldn't receive the "home button event" when the user really is closing the attention screen (the same behavior closing apps) and this behavior should be done in system app. Another idea will be about returning when we receive the "home button event" while document.hidden === true, perhaps it could work if the root cause is that
What do you think Ran?
Thanks
Updated•11 years ago
|
Flags: needinfo?(crdlc)
Comment 9•11 years ago
|
||
I think the correct approach would be not to receive the "home button" event in that case. Just as closing an app returns to homescreen but doesn't execute the event in it.
Comment 10•11 years ago
|
||
and what about ignoring the home button event when document.hidden === true?
Comment 11•11 years ago
|
||
I know it seems trivial but might be risky.
Comment 12•11 years ago
|
||
I kind of lost track of the nature of this bug
If this is a UX discussion, then the answer is that if the user opens an app while in the context of search results (whether it's from within the results, notifications or incoming call) they should return to the search results when they're done.
Is this the current behavior?
Flags: needinfo?(ran)
Comment 13•11 years ago
|
||
Yosef, this is not a UX discussion but a technical one. The required behavior is understood.
Christian, I personally think this should be handled in Gaia:System or Gaia:Dialer. Still, if you'd like to implement your solution (which will work), plz go ahead assign it to Gaia:Homescreen.
John, I propose to change the bug title to "Homescreen does not appear preserved during a call" due to Comment #6.
Assignee: ran → nobody
Component: Gaia::Everything.me → Gaia
Flags: needinfo?(ran)
Updated•11 years ago
|
status-b2g-v1.3T:
--- → affected
Whiteboard: 1.3tarakorun2
Comment 14•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•