@blakesteve/roster 4.9.0 → 4.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -0
- package/dist/meta.json +2 -2
- package/dist/roster.cjs.js +1 -1
- package/dist/roster.css +1 -1
- package/dist/roster.es.js +82 -19
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -194,6 +194,36 @@ by `src/contrast.test.ts`, at rest **and** on hover, in both themes.
|
|
|
194
194
|
object under WCAG 1.4.11, not text. It used to be excluded from the suite
|
|
195
195
|
entirely, which measured it against nothing.
|
|
196
196
|
|
|
197
|
+
`CallToAction` is **not** in that suite, and its light surface changed: the
|
|
198
|
+
fills moved a ramp step and the borders moved four, because the old surface
|
|
199
|
+
measured 1.03:1 against a light page with a 1.30:1 border — a banner you could
|
|
200
|
+
not see. **Installing this version changes how your existing CTAs look**, the
|
|
201
|
+
same way the 1.4.11 pass changed every field in 4.8.2. Its `info` variant also
|
|
202
|
+
moves from Tailwind's stock `blue-*` to Roster's `info-*`, so it now answers to
|
|
203
|
+
`--roster-info-*` like every other scheme.
|
|
204
|
+
|
|
205
|
+
Worth knowing what that border step is and is not. It is a **prominence**
|
|
206
|
+
decision, not a 1.4.11 one: a tinted banner is not a control, so the criterion
|
|
207
|
+
no longer reaches it once the surface has a fill. A call to action is the one
|
|
208
|
+
component whose job is to be looked at first, so it is deliberately the most
|
|
209
|
+
defined bordered block in the library. The filled surfaces it sits beside are
|
|
210
|
+
much fainter — `Card` soft at 1.04:1, `ErrorState` at 1.39:1, `Toast` and
|
|
211
|
+
`Pill` between 1.34:1 and 1.82:1. `Alert` is the closest, and only because its
|
|
212
|
+
4px left stripe is already a `-500`, at 6.10:1 for primary.
|
|
213
|
+
|
|
214
|
+
`CallToAction` and `Countdown` also lay themselves out with **CSS container
|
|
215
|
+
queries** rather than `md:` and `sm:`. The switch is now the CARD's width, not
|
|
216
|
+
the window's — a 228px card on a 1200px page used to lay out as a row and
|
|
217
|
+
squeeze its own text until it overflowed. Three things follow:
|
|
218
|
+
|
|
219
|
+
- **The breakpoint number changed** from a 768px viewport to a 512px card. A
|
|
220
|
+
CTA in a narrow page column will stack where it did not before.
|
|
221
|
+
- **`container-type: inline-size` collapses inside a content-sized ancestor.**
|
|
222
|
+
Give any `width: fit-content`, `inline-block` or table-cell ancestor a
|
|
223
|
+
definite width, or the card measures zero.
|
|
224
|
+
- **Container queries are required**: Chrome 105+, Safari 16+, Firefox 110+.
|
|
225
|
+
Without them a `CallToAction` renders in its narrow form at every width.
|
|
226
|
+
|
|
197
227
|
#### Ink follows the fill
|
|
198
228
|
|
|
199
229
|
The foreground is a token per fill, not per family:
|
package/dist/meta.json
CHANGED