chore: version packages - #579
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
blove
enabled auto-merge (squash)
September 4, 2026 17:13
Contributor
Vercel preview readyPreview: https://pretable-mwzs1wpmx-cacheplane.vercel.app Updated automatically by the |
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
@pretable/react@0.15.3
Patch Changes
2d7de95]:@pretable/ui@0.15.3
Patch Changes
The grid now answers two platform accessibility settings it was ignoring, and (#578)
every theme declares its
color-scheme.Forced colours (Windows High Contrast). A range selection was invisible.
The fill is a translucent
background-image, and forced colours drop the imageand force the colour underneath to
Canvas— so eleven selected cells came outidentical to no selection at all, with only the single focused cell marked, and
what the grid was about to copy could not be read off the screen. Selected cells
now take
Highlight/HighlightText, the pair the platform guarantees againsteach other, with
forced-color-adjust: noneso Chromium's text backplate doesnot paint an opaque rectangle over every word (it did; the computed styles were
identical either way and only a screenshot told them apart). Descendants inherit
the cell's colour, so a red P&L inside a selection cannot paint itself onto the
fill at whatever contrast it happened to have. Disabled menu items take
GrayText. The rest of the grid needed nothing: the border cage carries thestructure, the row-select glyph is drawn in
currentColor, and the frozen edgefalls back to the pinned cell's own border.
Reduced motion.
grid.cssanimated three things and offered no way out; aconsumer cannot patch that without re-implementing rules they do not own. All
three are decoration and are now switched off under
prefers-reduced-motion: reduce, with a guard that fails if a future animationis not named there too.
color-scheme. Onlypretable.cssdeclared it, so an Excel- orMaterial-themed grid kept light scrollbars and a light
<select>popup inside adark app — the one part of the surface a theme cannot reach with a custom
property. Both now declare it, Material in each mode it ships.
@pretable/core@0.15.3
@pretable/stream-adapter@0.15.3