Re: [csswg-drafts] [css-align] fully specify the "Overflow and Scroll Positions" section

The CSS Working Group just discussed `fully specify the "Overflow and Scroll Positions" section`, and agreed to the following:

* `RESOLVED: take this approach and file separate issues for wording issues`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: fully specify the "Overflow and Scroll Positions" section<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1425#issuecomment-413375688<br>
&lt;dael> astearns: fantasai and TabAtkins made edits. Are you asking for dbaron approval?<br>
&lt;dael> fantasai: It looks like we discussed but didn't resolve. Need to resolve and get dbaron review<br>
&lt;dael> fantasai: We were trying to spec the behavior of the content alignment properties on scroll containers. content alignment when applied to element it adjusts content inside it<br>
&lt;dael> fantasai: dbaron asked to tighten. We noticed what we were doing fundementally for a scroll container instead of align by layout and then clipping the alignment instead you're doing safe alginment and then scroll so you get effected alignment<br>
&lt;dael> fantasai: If you said align-conntent:end and the content overflows we start align and then scroll container so you get same effect as if not scroll cotnainer<br>
&lt;dael> fantasai: Tricky thing is scrollable overflow doesn't include padding at bottom. Well, might o r might now depending on UA...open issue  on overflow 3. When you scroll to the end the bottom of the visible content that overflows lines up with t he padding edge of scroll cotnainer. needs to be content edge for proper behavior.<br>
&lt;dael> fantasai: To get that alignment effect we're going for so switch between scrollable and not alignment is same we had to spec we extend scrollable overflow area by t hat amount of padding. We extend from edge of inflow content<br>
&lt;dael> fantasai: Authors have asked us to add this.<br>
&lt;dael> fantasai: We have a normal vallue for alignment that lets us do whatever weird things needed for compat. We trigger this extra space for scrollable overflow when you have a not normal value of align or justify content. That's new in spec because didn't look at implications of padding<br>
&lt;dael> fantasai: Asking WG if this is  okay and ask for review<br>
&lt;dael> fantasai: Questions or need explanation?<br>
&lt;dael> astearns: Little weird we trigger this on non-normal but I see why it's necessary<br>
&lt;dael> astearns: dbaron comments? Want more time?<br>
&lt;dael> dbaron: Need more time to review<br>
&lt;dael> astearns: Fair enough<br>
&lt;dael> astearns: Other comments?<br>
&lt;dael> fremy: Like the global idea. Haven't checked details<br>
&lt;dael> fantasai: Resolve on global idea and check wording later?<br>
&lt;dael> fantasai: Then we have WG resolved this is behavior we want. Problems with wording can file a specific issue<br>
&lt;dael> florian: If we could do away with odd compat it would be great. not realistic. This approach does seem to work all but a bit strangely.<br>
&lt;dael> florian: Can't think of anything simplier that works and respects compat<br>
&lt;dael> astearns: Objections to resolve to take this approach and filed separate issues for wording issues?<br>
&lt;dael> RESOLVED: take this approach and file separate issues for wording issues<br>
</details>


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

Received on Wednesday, 29 August 2018 16:17:53 UTC