Re: [css-snappoints][css-scroll-snap] scroll-snap-point-type and scroll-snap-align on the same element

On Mon, Jan 25, 2016 at 6:36 PM, Florian Rivoal <florian@rivoal.net> wrote:
>> On Jan 26, 2016, at 04:25, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> It's just like how align-content works on
>> the parent but align-self works on the child; you can meaningfully put
>> both on the same element, but they're doing different things in
>> different contexts, not interacting with each other.
>
> Right, that's how I expected things to work but I couldn't find which part of the spec says that explicitly, so I wasn't sure, and then wondered if it might be something else.
>
> In the css-scroll-snap, the descriptions scroll-snap-align and scroll-snap-type do not speak of ancestors or descendants, and that's where I was looking for this info. I now have found where you say that: In section 4 https://drafts.csswg.org/css-scroll-snap/#snap-model: "Snap positions must only affect the nearest ancestor (on the element’s containing block chain) scroll container."
>
> Matt's spec is clearer about this: that same sentence is in the overview, but in addition, the description of scroll-snap-align explains things in terms of ancestors or descendants. As you work with Matt to align the two specs, I suggest to align to his phrasing for this.

I think I've done so now - I defined what a scroll snap container is
(your nearest ancestor that does the right thing) and that you get
aligned in your scroll snap container.

~TJ

Received on Wednesday, 6 April 2016 23:26:46 UTC