Closed Bug 878732 Opened 11 years ago Closed 11 years ago

Homescreen gets stuck between everything.me screen and time display

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: eflores, Assigned: crdlc)

Details

Attachments

(1 file)

On nightly branch

STR:
1. Restart b2g
2. At homescreen time display, swipe right to start e.me loading
3. While e.me screen is loading, swipe left to partially reveal time display and hold in that position until e.me is finished loading
4. Release

Expected:
Homescreen should spring back to either time display or e.me

Actual:
Homescreen gets stuck between the two screens
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Attached file Patch v1
Attachment #757401 - Flags: review?(evyatar)
cristian- I understand the patch and it's a cool and easy solution- but it doesn't seem to work on my device (Unagi). I can still when loading...
umm I cannot reproduce it, I gonna take a look tomorrow better, thanks
Cristian, any insights?
Do you prefer us at e.me just take it?
Flags: needinfo?(crdlc)
Hi, I gonna try to reproduce it during this morning if I cannot, I'll pass you the bug :) Thanks
Flags: needinfo?(crdlc)
It works fine for me with this patch, could you provide me with new STR? Thanks a lot
ok you're right- after the patch, when holding the swipe between e.me and landing, and then releasing- it fixes itself correctly.
Attachment #757401 - Flags: review?(evyatar) → review+
https://github.com/mozilla-b2g/gaia/commit/a77a4185859c58b78eff85d0ed6a738184685eaa
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment on attachment 757401 [details]
Patch v1

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 #): 
User impact if declined: low because IMHO the STR are weird for common final users and furthermore they can recover the state touching the screen but the reporter demonstrated that is possible and how the risk is null I would like to add to v1-train branch
Testing completed: yes
Risk to taking this patch (and alternatives if risky): null, only one CSS rule was added so I considered that it could be on v1-train
String or UUID changes made by this patch:
Attachment #757401 - Flags: approval-gaia-v1?
Comment on attachment 757401 [details]
Patch v1

Approvals are now closed. Please nominate for blocking-b2g:leo? for critical issues.
Attachment #757401 - Flags: approval-gaia-v1?
It is not critical but the risk is null and nice to have
blocking-b2g: --- → leo?
Triage - low impact, easy recovery, nonblocking.
blocking-b2g: leo? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: