Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
The W3C publishes Candidate Recommendation drafts describing oklch(), lab(), and related gamut mapping used by evergreen browsers.
Design tokens should store both authored and display-referred values carefully.
Understanding display: inline-flex vs block-level boxes requires reading the Display spec alongside Box Alignment modules.
Layout bugs often trace to mixed writing modes.
Layer ordering impacts specificity resolution; teams adopt @layer to sandbox component styles from utility frameworks.
Document layer graphs in style guides to prevent circular imports.
Subgrid enables nested grids to align to parent tracks; consult Grid Level 2 for track sizing interactions.
Test Firefox and Safari behavior differences with reduced cases.
Web-platform Interop dashboards highlight which CSS properties receive focus fixes each year—useful when prioritizing QA budgets.
Pair with WPT results linked from specs.
OKLCH improves perceptual uniformity but requires fallbacks for older engines; the Color Level 4 spec explains interpolation behavior.
Keep sRGB hex backups for export to legacy PDF pipelines.
Cascade 4 defines how !important reverses normal layer ordering; misuse creates debugging nightmares—prefer structured layers over !important.
Illustrate layer order diagrams in PR descriptions.
Grid Level 2 specifies which line names and sizes propagate; implicit track patterns differ from explicit templates.
Use devtools grid overlays while prototyping.
Box Alignment Level 3 defines safe overflow behavior for centered clusters; critical for small viewports and dynamic type.
Combine with media queries for coarse pointers targets.
Import or adapt Web Platform Tests cases relevant to your property; many specs link to directories in the WPT repository.
Automate screenshot diffing only after reducing flakiness.