Re: [csswg-drafts] [css-scroll-snap-1] Path to interop among implementations

The Working Group just discussed `css-scroll-snap`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: css-scroll-snap<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2523<br>
&lt;dael> majidvp: Chrome we're impl scroll-snap. We're close to shipping. I tried to understand what other browsers impl. They're completely different.<br>
&lt;dael> majidvp: In 2016 WG resolved to fundamentally change the spec. Older spec mostly coordinate based and new is element based. New model I htink is fundimentally better because it lets UA make a better decision.<br>
&lt;dael> majidvp: At the time I think all impl agreed it's good and spec is in CR.<br>
&lt;dael> majidvp: Only Safari impl matches spec. Mozilla ships unprefixed old spec and I see a bug a few years ago for that. Same with Edge/IE they're an even older version os the spec.<br>
&lt;dael> majidvp: 2 vendors impl old, Safari is close to new, Chrome will ship close to Safari but prob cover more spec.<br>
&lt;dael> majidvp: Wanted to see if there's updates from other vendors.<br>
&lt;dael> fantasai: I'd like to mention it's important that whoever impl scroll padding and ships impl the behavior spec to apply to containers without snapping turned on. If we want that to ever work it needs to work when you turn on scroll padding so people can detect it exists.<br>
&lt;fantasai> s/scroll padding/scroll-padding/<br>
&lt;dael> astearns: Comment from Edge folks?<br>
&lt;dael> Rossen: Looking for current status.<br>
&lt;dael> florian: I think it says you plan to do it.<br>
&lt;dael> Rossen: We haven't started work. Under considerations.<br>
&lt;dael> dbaron: I think updating we looked at doing in the medium term. Possibly in next year, not next few months.<br>
&lt;tantek> For reference: our (Mozilla) bug to update to the scroll-snap CR: https://bugzilla.mozilla.org/show_bug.cgi?id=1231777<br>
&lt;dael> majidvp: I wouldn't be surprised that since there's an impl that switching to element based won't be hard to do. Safari I think managed to switch the modal. Seems reasonably straight forward.<br>
&lt;tantek> It's also in our 2018 priorities though we're not sure we'll get to it: https://wiki.mozilla.org/CSS#2018_Priorities<br>
&lt;dael> smfr: Impl wasn't too bad. Some compat problems.<br>
&lt;tantek> s/get to it/get to it in 2018<br>
&lt;dael> majidvp: Seems that for next year the old impl will exist. Next topic is if we should have explicit comments on how to migrate from the old snap points syntax to migrate to the new and if there's a subset of old that can be used.<br>
&lt;dael> majidvp: For example, old had destination and coordinates and they would align. Similar enough to the new spec that if you impl you can use the old and new models at the same time. We should have comments that this is safe to do, but don't use old.<br>
&lt;dael> tantek: I'd rather not encourage authors to use any old syntaxes to reduce compat shadow we create as a whole. I don't think we should rec older syntaxes.<br>
&lt;dael> florian: I've made demos that work in both old and new and you have to use both syntaxes but that's all you can do.<br>
&lt;dael> tantek: We don't want to support old going forward and if someone uses it because there's documentation on how to do it it increases the risk.<br>
&lt;dael> tantek: You increase the risk people create more stuff on the web with the old.<br>
&lt;dael> astearns: That they'll create stuff with old and new so it doesn't break when you move.<br>
&lt;dael> majidvp: But it would be hard to measure they used both. I think I agree encouraging using both may not be right. w<br>
&lt;dael> astearns: Anything more?<br>
&lt;dael> majidvp: One last thing, spec didn't have tests. AS we impl we added tests, but I wanted to make a suggestion to other impl that as they impl it would be nice to have more tests.<br>
&lt;dael> florian: I'm not impl but considering writing some tests. It's nice you've got basic and I'll ping you to get a review when I write for edge cases.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2523#issuecomment-380421207 using your GitHub account

Received on Wednesday, 11 April 2018 11:37:14 UTC