Closed
Bug 829090
Opened 12 years ago
Closed 11 years ago
Sometimes Gecko failed to render lock screen "fly out" transition
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: timdream, Assigned: rik)
References
Details
(Keywords: perf, Whiteboard: [c= p= s= u=] ux-tracking)
+++ This bug was initially created as a clone of Bug #804193 +++
Bug #804193 have since marked fixed because it fixes a related Gaia incorrect implementation, but we would still need Gecko to fix the skipped transition.
Yuren had concluded that we could reliably reproduce this if the screen was turned off while we are on Everything.me panel.
And no, bug 824454 doesn't fix this, unfortunately.
Our best bet at the moment is a workaround-ish approach like bug 827382. We can "peek" the transition in by setting lockscreen opacity to 0.99 or something, and then finish off the normal transition after that.
etienne can advise ;).
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → anthony
Comment 2•12 years ago
|
||
Am still seeing this issue (failure to render lock screen hint animation) in my current build (Unagi, beta, updated 3/12). Marking ux-most-wanted for usability impact (we've had multiple reports of users not discovering the unlock gesture).
Whiteboard: visual design, interaction, BerlinWW → u=user c=system s=ux-most-wanted
Updated•11 years ago
|
Whiteboard: u=user c=system s=ux-most-wanted → ux-tracking
Updated•11 years ago
|
Whiteboard: ux-tracking → ux-tracking, hanzo, visual-tracking
Updated•11 years ago
|
Priority: P3 → --
Whiteboard: ux-tracking, hanzo, visual-tracking → [c= p= s= u=] ux-tracking, hanzo, visual-tracking
Updated•11 years ago
|
Whiteboard: [c= p= s= u=] ux-tracking, hanzo, visual-tracking → [c= p= s= u=] ux-tracking
Comment 3•11 years ago
|
||
Lockscreen has been reimplemented in 1.2 and when tested against 1.2 this issue no longer reproduces.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•