Re: [csswg-drafts] [css-scroll-snap-1] Compat between webkit and blink/gecko regarding "implicit" scroll boundary snap positions (#4037)

The CSS Working Group just discussed `[css-scroll-snap-1] Compat between webkit and blink/gecko regarding "implicit" scroll boundary snap positions`, and agreed to the following:

* `RESOLVED: Close no change based on reasoning in https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-538060075`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-scroll-snap-1] Compat between webkit and blink/gecko regarding "implicit" scroll boundary snap positions<br>
&lt;Rossen_> https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-590372507<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-590372507<br>
&lt;dael> Rossen_: Reopened with additional thoughts<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-538060075<br>
&lt;dael> fantasai: Prop is close no change based on majid's reasoning based on ^ comment<br>
&lt;fantasai> per that comment, close as no change<br>
&lt;dael> fantasai: Means WebKit needs to fix to not have implied start and stop points. That's how I propose to close.<br>
&lt;dael> Rossen_: I see smfr added a tracking bug?<br>
&lt;dael> smfr: This is on my radar and fine<br>
&lt;dael> Rossen_: Objections to close no change?<br>
&lt;dael> RESOLVED: Close no change based on reasoning in https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-538060075<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config