CSS WG Blog Minutes Telecon 2016-01-27

Minutes Telecon 2016-01-27

• Resolved: Accept the new language as suggested in option B of this e-mail.
• There were still concerns about avoiding behavior that feels bad to a user when using 2D scrolling, especially when combined with mandatory.
• Resolved: Bring 2D snapping into the Snap Points spec and mark as at-risk.
• There were varied opinions on if there needs to be more terminology around the viewport to distinguish between different types.
  • MaRakow reported he wasn’t blocked on this, so a decision wasn’t needed right away.
  • It was agreed that the viewport terminology should be defined in device adapt, overflow, or the viewport specs.
• fantasai explained that she believed having scroll-snap-padding and scroll-snap-margin physical and scroll-snap-align logical makes sense because scroll-snap-align interacts with the scrollers which operate in logical direction.
  • MaRakow felt that her example case didn’t deal with the case when the user sets two properties on a 1D scroll. He’ll make another example case to further the conversation.
• The bikeshedding of the properties currently called mandatory and proximity will happen at the F2F, but it was agreed that the names should be improved.
• The short conversation on splitting scroll-snap-type seemed to indicate approval of the split, but naming will wait until the F2F.

Full Minutes

« Previous article Next article »