Switched from using deviceorientation to orientationchange. #220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Switched from using deviceorientation to orientationchange.
|
Thank you, released as v2.8.9. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The deviceorientation event is fired when a device's physical orientation changes per the w3c spec, not necessarily when the orientation changes itself.
Previously, if the device was tilted or moved in an inconsequential manner, it was firing off the logic to recalculate the height. With the orientationchange event, when the layout itself switches from portrait to landscape it is now recalculating the height.
I also upgraded grunt-contrib-uglify library so that I could build.