CSS WG Blog – Minutes San Francisco F2F 2016-05-11 Part II: Scroll Snapping, Color, Grid, Flexbox, Inline

This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.

Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.

Minutes San Francisco F2F 2016-05-11 Part II: Scroll Snapping, Color, Grid, Flexbox, Inline

By Dael Jackson June 18, 2016 (Permalink)
Categories: resolutions

Scroll Snapping

Archival Copy of the Change Proposal being discussed available here

Resolved: No ability to specify the strictness of snapping separately per axis.
Resolved: Allow the keyword to be dropped, default to proximity.
Resolved: Ordering of keywords is strict in scroll-snap-type (to allow for extensions)
Resolved: Values are x | y | block | inline | both | point , where point would be dropped after next publication.
Resolved: Require (for now) an explicit axis and will gather more info as we can (to decide between physical and logical direction as the default).
Resolved: Make snap-align behave like a subset of background position (from fantasai’s proposal).
Resolved: Add section 6.2.2 (Snapping Boxes that Overflow the Scrollport) and add issues.
Resolved: Add section 6.2.1 (Scoping Valid Snap Positions to Visible Boxes) as an open issue
Resolved: Add section 6.2.3 (Unreachable Snap Areas)
Resolved: Merge section 6.3 (scroll-snap-stop) with an issue about whether it applies to 2D and an issue to bikeshed “normal”
Resolved: Merge section 7.3 (Choosing Snap Positions) with A parenthetical of “corridor” point moved to start the paragraph and JS element-targetting scrolls added into the :target paragraph
Resolved: Add section 7.1 after removing “explicit” “inertial” and “directional” definitions, moving the first sentence and adding a more precise definition of when an active scrolling operation is done so we know when to start snapping.
Resolved: Merge 7.0 (introductory text) too
Resolved: Add fantasai and TabAtkins as editors to scroll snapping
Resolved: Shortname css-snappoints -> css-scroll-snap

Full Minutes || Spec Referenced

CSS Color

There were several actions recorded to make improvements to the spec. They were to:
- add note explaining a reasonable range for C in lch to the spec
- remove commas between in the color examples
- fix Rec.2020 and Rec2020 to be rec2020, and DCI-P3 P3 to either (consistently) dci-p3 or p3
- color fallback should be like font list fallback.
- add a working-color-space at-rule, which affects the entire document
The breakout session proposed resolving to publish WD for Color and MQ4.
Resolved: Do black point compensation when converting from profile to another.
Resolved: If you accurately describe the output device’s color profile in an @color-profile rule then a sane implementation will not alter your colors so this is sufficient as a replacement for device-cmyk in general and provides a good RGB fallback automatically.