Following is simple html, when viewed on android browser(nexus one) results into continuos orientationchange event chain when you change phone's orientation just once.
Can somebody please explain and suggest some workaround?
orientationchange is fired spuriously: opening an alert dialog, or opening the browser menu fires it, and it often fires more than once. So, opening the alert menu causes an event loop, which means that the browser has to be killed manually--it lacks even basic protection against alert loops and it renders the menu inaccessible.
(I don't understand any production browser that can be taken out by
I think Falmarri means that by default that is what happens. You can prevent it from happening and listen for configuration changes in your activity, and then rotate the screen yourself, then the activity isn't restarted. See this series on rotation.
These devices seem to trigger an 'orientationchange' event before the window is resized to reflect the new orientation.
How to fixed this: github
©2020 All rights reserved.