Closed Bug 840126 Opened 11 years ago Closed 9 years ago

Launching app in manifest-declared orientation results in slow and flickering UI rotation

Categories

(Firefox OS Graveyard :: General, defect, P3)

ARM
Gonk (Firefox OS)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Harald, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c= p= u= s=])

Expected behavior: Setting orientation in the manifest should launch the app smoothly in the right orientation, without flickering and glitches.

Current behavior: While holding the phone in portrait, the user launches a game that declared orientation landscape in its manifest. The user will see a flickering between the game launch-screenshot in portrait; a black screen; the cut off gray-rocket background with white margins; ending with the app finally being in landscape.

Reproduce: Install packaged app with orientation set to landscape in manifest.
There's a similar problem that I need to file that involves the case when you close the app.
This is very likely a problem on the Gaia side (the transition). It could be the Gonk's screen orientation backend too.
Keywords: perf
Whiteboard: [c= p= u= s=]
Assignee: nobody → alive
Working on bug 908601 and I saw this, taken as well.
Alive, any update on this?
Flags: needinfo?(alive)
https://bugzilla.mozilla.org/show_bug.cgi?id=908601
Solves this by disabling opening/closing transition if app's default orientation is perpendicular to current orientation.

I'm afraid we have a platform issue here(If resize happens before animation, then the animation fails), may need some gfx guy to look. I suggest to keep this opened.
Flags: needinfo?(alive)
Thanks Alive. +Milan for Graphics; please see Alive's comment 5.
I'll need info on this to keep track; is there any push for this getting elevated to 1.2 or 1.3?  Just want to know the urgency.
Flags: needinfo?(milan)
Milan, no urgency for 1.2 or 1.3.
CC-ing Brian in case Comment 5 is relevant to his current work.
A reduced test case would really help here. Do you know if it's B2G only? If it's OMTA-related I can look into it but if it's an issue about triggering transitions in general then dbaron is the one to ask. I think there is still some outstanding work to bring us into line with the latest changes to the transitions spec.
Flags: needinfo?(alive)
I don't think it's b2g only but it's only on device now.. I guess it's relevant to hardware limitation.

How about that if I made a patch for you to get the transition back?
Flags: needinfo?(alive)
(In reply to Alive Kuo [:alive][NEEDINFO!][:艾莉芙] from comment #11)
> I don't think it's b2g only but it's only on device now.. I guess it's
> relevant to hardware limitation.
> 
> How about that if I made a patch for you to get the transition back?

Is there any delay (transition-delay or animation-delay) involved? And, it's using CSS transitions right, not CSS animations?
(In reply to Brian Birtles (:birtles) from comment #12)
> (In reply to Alive Kuo [:alive][NEEDINFO!][:艾莉芙] from comment #11)
> > I don't think it's b2g only but it's only on device now.. I guess it's
> > relevant to hardware limitation.
> > 
> > How about that if I made a patch for you to get the transition back?
> 
> Is there any delay (transition-delay or animation-delay) involved? And, it's
> using CSS transitions right, not CSS animations?

Sorry for late response.
No delay specified.
Use either animation or transition doesn't matter here.
Alive, do you know if any work has been done towards this?
Flags: needinfo?(alive)
Priority: -- → P3
No, de-assigning.

BTW I am posting a orientation regard article to webapi, and launching perpendicular apps need UX confirm in bug 985843.
Assignee: alive → nobody
Flags: needinfo?(alive)
Flags: needinfo?(milan)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.