chore: version packages - #274
Merged
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
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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tenphi/tasty@3.3.1
Patch Changes
#273
5cea972Thanks @tenphi! -#currentcompiles to thecurrentcolorkeyword again, as it did before 3.3.0.3.3.0 made it emit
var(--current-color)so that a token defined as#currentcould be faded on Safari 16.4 rather than 18 — relative color syntax takes a
concrete origin from 16.4, while
oklch(from currentcolor …)needs 18. Thattraded away the property
#currentexists for.The keyword resolves against the element that reads it, so a
#currentunder anancestor that faded its own color reads the faded color. A ramp built on
#currentdepends on it: the disabled state is expressed once, incolor, andeverything painted from
#currentbelow fades with it. The variable cannot dothat — a faded color is deliberately never published into
--current-color(resolving it a second time one level down would fade it twice), so a reader saw
through to the unfaded color above and rendered at full strength.
The variable itself stays, and keeps both improvements 3.3.0 brought it. It
carries the inherited color for consumers that need it as a color rather than as
the keyword — hand-authored CSS, or anywhere the keyword will not do. Read it as
$current-color:nearest
colorrather than the nearest token color.initial-value: currentcolor, so where nothing publishedit a reader still resolves against its own element.
The case 3.3.0 set out to fix goes back to needing Safari 18: a token defined as
#currentand then faded —{ '#ink': '#current', fill: '#ink.5' }— givesrelative color syntax a
currentcolororigin. Put the fade in the token instead,{ '#ink': '#current.5' }, and it goes throughcolor-mix()on the Safari 16.2floor.