- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jan 2022 11:36:23 +0000
- To: public-css-archive@w3.org
> > 2. Talking of setting the scroll position with x and y coordinates, why not use a `<position>` value for that? > > i suppose this could get discussed more, but i do still feel like `<length-percentage>` works better here? curious what the tradeoffs are. The tradeoff using `<position>` is that it forces the order to be horizontal first then vertical, which might not be the order you'd expect in this case. Though it provides every functionality related to positioning and additional features to just `<length-percentage>` (which is included, btw.) like offsetting from the center, for example. > > 3. What happens when multiple scroll container children have scroll-start-target defined? > > Explainer says it's the 1st in the DOM order with the property. So competition is resolved by 1st node found. Matches your proposal too it looks like. I don't see that in the explainer, though if it's meant to match my proposal, it's fine for me. 😄 > > 4. Both properties do the same thing, except one is set on the container, the other on a child? > > Like scroll-snap, some of the style is specified by the scrollview and some by a child. My point was that it's not strictly necessary to have two properties for that because the use cases can be covered by a single one. Though I don't have a strong opposition against adding two. > The original explainer used `selector()` but I agree with other CSSWG members that `selector()` circumvents CSS's natural selection mechanism. So, the workflow maps closer to scroll-snap, where a child needs to specify the property on itself. No new functions need required for the feature, which is nice. Just for the record, `selector()` is not new. See the related issue #5811. My first point still stands, though. The names should be chosen so that it's clear that they don't have a shorthand-longhand relation. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6986#issuecomment-1024132310 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 January 2022 11:36:25 UTC