border-image: Add compat_features and baseline status
#160
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
foolip
approved these changes
May 4, 2023
There was a problem hiding this comment.
I think this is correct. The inclusion in Interop 2023 is to fix some rough edges. Looking at web-platform-tests/interop#146 I think it could make sense to link to https://bugs.chromium.org/p/chromium/issues/detail?id=767352 in BCD, which was recently fixed.
|
@foolip Thank you! I opened a PR against BCD for the bug fix. Merging now. |
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 adds compat features and a baseline status to
border-image.This one is interesting because the data says this enjoys longstanding support, but its inclusion into Interop 2023 makes me doubt it. The only thing in BCD itself which hints at this is lengthy notes on Firefox's support for
border-imageandborder-image-slice. But the Interop dashboard graph makes it look like Chrome and Safari lagged significantly, but no notes indicate why that might be. 🤔