Fix "border-image fail" bug in Chrome #4
Merged
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
|
Thanks! How much does this affect the time taken (it's on the sidebar)? That's the reason I kept it out of the document, for performance. |
|
Um, I have a good computer so I dont see any difference, I get around 50-51ms on both with and without the patch. |
LeaVerou
added a commit
that referenced
this pull request
Feb 2, 2012
Fix "border-image fail" bug in Chrome
|
Ok, lets try it. Thanks again! |
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.
This is certainly a bug in Chrome, but I found a solution. Strangely if you add the variable dummy to document or do a console.log on dummy, the border-image will not fail anymore.