Issues · w3c/csswg-drafts · GitHub

Labels Milestones New issue

[css-contain] `scroll-state(stuck)` CQs can easily cause flickering that is very hard to work around

#13898

· LeaVerou opened

on May 7, 2026

[css-nav][css-contain] Navigation containment

#13142

· Crissov opened

on Nov 23, 2025

[css-contain-2] text-overflow property should not be mentioned

#12157

· Psychpsyo opened

on May 4, 2025

[css-contain] Should `contentvisibilityautostatechange` events bubble?

#11310

· knowler opened

on Dec 2, 2024

[css-values-4][Editorial] `<condition>` type that other specs reference

Closed Accepted by CSSWG Resolution

css-conditional-3

css-conditional-4

css-conditional-5

#10457

· LeaVerou opened

on Jun 17, 2024

[css-contain] Describe generalized goals containment

#10382

· frivoal opened

on May 31, 2024

[css-contain] content-visibility: auto and SVG-as-image

#10347

· emilio opened

on May 17, 2024

[css-images-4] Should `contain-intrinsic-size` affect `object-fit`?

Closed Accepted by CSSWG Resolution

#10116

· eeeps opened

on Mar 21, 2024

[css-contain][css-scroll-anchoring] Scroll into view adjustments for content-visibility: auto

#9833

· flackr opened

on Jan 22, 2024

[css-contain-2]: Should the first `contentvisibilityautostatechange` event be fired without knowing if the element is close to the viewport

#9803

· cathiechen opened

on Jan 16, 2024

[css-contain-2] Consider forcing layout on content that is skipped when querying it on an element with content-visibility

#9675

· nt1m opened

on Dec 4, 2023

[css-contain] add new value where content is visually hidden, but exposed to accessibility tree

#9579

· Schepp opened

on Nov 9, 2023