Both BCD and caniuse have a concept of partial support. Examples:
https://developer.mozilla.org/en-US/docs/Web/API/ScreenOrientation/lock#browser_compatibility
https://caniuse.com/webp
We have already accumulated a number of features that could benefit from the same:
|
# TODO: Add notes about animated AVIF coming later in Safari (but don't mark this as partially supported) |
|
# TODO: Consider notes or partial implementation for Safari 10.1 due to the |
|
# lack of support for nomodule. It's important for fallback behavior, but in |
|
# the long term not important if JS modules support is completely ubiquitous. |
|
# TODO: Add notes about animated WebP coming later in Chrome (but don't mark this as partially supported) |
#912 is another case currently in review.
In BCD, partial_implementation must come with a note, and we should probably do the same.
Both BCD and caniuse have a concept of partial support. Examples:
https://developer.mozilla.org/en-US/docs/Web/API/ScreenOrientation/lock#browser_compatibility
https://caniuse.com/webp
We have already accumulated a number of features that could benefit from the same:
web-features/feature-group-definitions/avif.yml
Line 6 in 477f11f
web-features/feature-group-definitions/js-modules.yml
Lines 12 to 14 in 477f11f
web-features/feature-group-definitions/webp.yml
Line 6 in 477f11f
#912 is another case currently in review.
In BCD,
partial_implementationmust come with a note, and we should probably do the same.