Split text-underline-offset from text-underline-position #2652
Conversation
This file contains hidden or 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
These properties are related, but they can be used individually. text-underline-position is signifcantly older in some browser. Usage is also quite different: https://chromestatus.com/metrics/css/timeline/popularity/405 https://chromestatus.com/metrics/css/timeline/popularity/661 The motivation for this is mapping the above use counters to counters for the web-features entries. They are technically easy to measure as one, but doing so seems unhelpful.
github-actions
bot
added
the
feature definition
captainbrosset
approved these changes
Feb 14, 2025
jamesnw
reviewed
Feb 20, 2025
Co-authored-by: James Stuckey Weber <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These properties are related, but they can be used individually.
text-underline-position is signifcantly older in some browser. Usage is
also quite different:
https://chromestatus.com/metrics/css/timeline/popularity/405
https://chromestatus.com/metrics/css/timeline/popularity/661
The motivation for this is mapping the above use counters to counters
for the web-features entries. They are technically easy to measure as
one, but doing so seems unhelpful.