CSS WG Blog – Minutes Paris F2F 2015-08-26 Part I: Round Display, Grid Layout, Animations, Scroll Snapping

Minutes Paris F2F 2015-08-26 Part I: Round Display, Grid Layout, Animations, Scroll Snapping

By Dael Jackson September 14, 2015 (Permalink)
Categories: resolutions

The representatives from LG presented their work on Round Display, including several demos of test cases.
The group thought the progress was good and the use cases compelling, though there was in expressed desire to have the spec written to apply more widely instead of focusing only on round displays.
Some pieces of the spec may ultimately belong in other existing specs, but for now they will be worked on here until they stabilize.
There were several issues to resolve, some editorial and some conceptual.
Resolved: Pending notation of any open issues in the draft, publish FPWD of Round Display
Resolved: Add Hyojin Song as an editor to round display, move Soonbo Han to former editor

Resolved: Switch row-gap/column-gap to grid-column-gap and grid-row-gap and maintain grid-gap as the shorthand name.
- It is possible that they will be named grid-gap-rows/grid-gap-columns instead depending on the results of polling.
Resolved: Stretch stretches auto-sized tracks only
Resolved: Add repeat(auto-fill) and repeat(auto-fit)
Resolved: Publish a new Grid WD after the above edits

The group agreed that the work on exposing the Animations APIs should move from a delta spec to a real spec, but felt that the edits to Animations level 1 should be made first, especially as it would make backporting easier.
Resolved: Add birtles as editor to Animations pending him getting added to the working group

fantasai and TabAtkins brought their proposal to re-think how the scroll-snap property works, especially in addressing what they do with oversized elements.
- The proposal was that whenever you snap to an element and it’s larger than the viewport in some axis, in the overflowing axis you then stop snapping to that element from now on and instead the edges become the new snap points.
  - This would also move the model of snap points from a point to point snap toward a box to box snap to accommodate more robust behavior.
- There were questions about the functionality of snapping to an edge in regards to it causing problems for those using arrow keys when the edge is very close to the viewport, such as 1px away.
- Several people indicated that they wanted to ensure the wording on this was loose enough that the UIs could do something smart.
There were several questions about the value and functionality of grouping and it was expressed that this was likely a level 2 behavior.
The renaming proposal of changing scroll-snap-destination to target had people on both sides of the fence, but ultimately will remain named as-is.
MaRakow, fantasai, and TabAtkins decided they would discuss further and come back to the group with a list of needed resolutions now that the broad re-thinking had been explained. Originally this was to happen after the lunch break, but the group needed more time.

Last updated 2015-09-14 20:52:05