Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Event order differs for platforms on orientation change

See original GitHub issue

Retrieving screen.width and screen.height in an change:bounds callback after rotating the device return different values on both platforms. On Android the updated screen.width and screen.height values get returned, while on iOS they are still the ones valid before the rotation.

Issue Analytics

State:
Created 9 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

jordiboehmecommented, Mar 5, 2015

Can you provide a small snippet to reproduce?

0reactions

ralfstxcommented, Mar 9, 2015

I agree that change:orientation should come before change:bounds.

Top Results From Across the Web

Handling Orientation Changes on Android - Medium

When you rotate your device and the screen changes orientation, Android usually destroys your application's existing Activities and Fragments and recreates them ...

Handle configuration changes - Android Developers

If you want to manually handle orientation changes in your app you must declare the "orientation" , "screenSize" , and "screenLayout" values in ......

Window: orientationchange event - Web APIs | MDN

The orientationchange event is fired when the orientation of the device has changed.

Handling orientation changes in React Native - Adrian Hall

I store the orientation in the state object, then add an event listener. Whenever the dimensions change (for example, due to an orientation...

How do I correctly detect orientation change using Phonegap ...

Update May 2019: window.orientation is a deprecated feature and not supported by most browsers according to MDN. The orientationchange event is associated with ......