Adding 'image-rendering: pixelated' to overcome antialias fuzziness 3 tests #41602
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 a follow-up to
#40715
#40731
Adding 'image-rendering: pixelated' in order to avoid or overcome subpixel antialias fuzziness in the following 3 border-image-repeat-* tests:
https://wpt.fyi/results/css/css-backgrounds/border-image-repeat-round-003.html
https://wpt.fyi/results/css/css-backgrounds/border-image-repeat-round-stretch-001.html
https://wpt.fyi/results/css/css-backgrounds/border-image-repeat-stretch-round-001.html
If this does not succeed, then I will resort to use
<meta name=fuzzy content="i, j">
Credits should go to @fantasai for those recommandations.
image-rendering: pixelated
appears to be supported well by current mainstream browsers as indicated by/according to:https://developer.mozilla.org/en-US/docs/Web/CSS/image-rendering#browser_compatibility