Closed Bug 993923 Opened 11 years ago Closed 11 years ago

Screen doesn't get updated when orientation changes 180 degrees

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 937713

People

(Reporter: graziani, Unassigned)

Details

In applications that allow orientation change (ex. Gallery, Browser), when the device is rotated by 180 degrees, the screen may take over than 10 seconds to be updated to the new position. STR: 1- Go to Gallery app with a few images (Browser app is ok too). 2- Rotate the device by 180 degrees (fast) Expected Result: - Screen should be updated to the new orientation Problem: - Screen takes over 10 seconds to be updated to the new position
I can confirm that mozorientationchange event is correctly delivered to Gaia. However Gaia apps do not handle this event. They just handle changes on screen size (that is why when I rotate the device in 90 degrees, the screen is updated).
Priority: -- → P2
Hi John, I saw you did some work related to orientation change in Gallery app... I wonder if Gaia app should also handle this mozorientationchange event in order to force the screen to be refreshed when a 180 degrees orientation happens, or if this case should be handled in Gecko somehow.
Flags: needinfo?(johu)
Priority: P2 → --
There was a collision when I posted my comment. Re-setting priority...
Priority: -- → P2
Gallery app doesn't handle mozOrientationChange by itself because we don't lock that in manifest. Such kind of orientation change should be handled by System app and Gecko both. System app tells gallery app the correct size of screen after rotated and Gecko flips the video buffer. IIRC, we had similar issue before. The UI takes a long time to rotate when orientation changed.
Flags: needinfo?(johu)
Bug 937713 is exactly the same and the patch landed there solved the problem. Master branch currently is ok.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.