Allow abs-sign to progress to Baseline low
#3205
Merged
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
github-actions
bot
added
the
feature definition
jamesnw
approved these changes
Aug 6, 2025
Collaborator
jamesnw
left a comment
jamesnw
left a comment
There was a problem hiding this comment.
This makes sense to me!
Elchi3
approved these changes
Aug 7, 2025
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.
In #3189, I put an editorial hold on
abs-sign, preventing it from advancing to Baseline low. This PR removes that override and allows the feature to advance, following the upstream data from BCD.After getting additional input in #3194 and reading the linked bugs, I came to the conclusion that mixed relative units are an embellishment on the behavior of
abs(),sign(), andcalc()rather than a missing factor inabs-signspecifically.Fixes #3194.