#88 - Fix IE9 Functionality #89
Closed
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
…Browsers that do support 3D will use that instead. Browsers that dont will fall back to translateX
Closed
|
Hey @nring, thank you for contributing to lory. This issue is already adressed, so I will close this one for now. For next time please also read what I mentioned to @levito about semantic release and commit messages. This is very important in order that we can merge and actually automatically build new releases. Will be online in the next couple of days :) cheers Max |
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
translateXtransform was removed in favor oftranslate3dback in release 1.2.3. That broke IE9 functionality. I'm adding it back in before translate3d. Browsers that do support 3D will use that, but browsers that don't (like IE9) will fall back totranslateX.