fix bug where images loaded from chrome cache results in 0 WIDTH elements #34
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
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 chrome versions (linux 54.0 being one of them) sometimes the
getComputedStyle(data.target[0]).widthcall inSpin.setLayoutreturns the valueautowhich makes the image width value 0 (w = Number(style.width.replace('px', ''))|0; === 0), thus making it invisible.It usually happens when spritesbin fully loaded the images, then you change to another page and then you go back to the previous page using the browser back button. My best guess is that chrome triggers the
img.onloadevent for cached images without (or before) computing the image dimensions.