Repository navigation
Conversation
This branch has not been deployed
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
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.
Description
Hex colors with alpha were rounded to one decimal when parsed, so values such as
#0000FF01became fully transparent and most 8-bit alpha values could not round-trip.toHex8()also truncated float alpha values instead of rounding them to the nearest byte.This change preserves the full alpha value from 4- and 8-digit hex colors and rounds alpha when serializing to
#RRGGBBAA. Regression coverage checks every 8-bit alpha value, every 4-bit shorthand alpha, low alpha, andrgba()serialization.Type of change
Checklist
pnpm lintpasses)pnpm testpasses)pnpm build)The focused Chromium suite passes all 126 color tests. The complete browser suite was not run locally.
Related issues
None.