Added support for slow DOM loading browser such as mobile devices #20
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
|
@Schwierig Are you initializing the plugin when the document is ready? |
|
Oh, I think I found that even window.onload doesn't fix this issue. I had to add a 100ms timeout and manually trigger unveil on the initial images. See my code at #7. |
|
I think this can be closed due to the fact that this doesn't fix the problem. |
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.
In some mobile browsers such as Chrome or Safari mobile the initial viewport images weren't loading without the user scrolling. This happened due to the fact that the images weren't even inserted into the DOM tree when unveil was initialized.
The added on-load event prevents this from happening.