W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2020

Re: [csswg-drafts] [css-overflow-3] Clarify padding-bottom in overflow content (#129)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 30 Sep 2020 17:02:32 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-701519671-1601485351-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-overflow-3] Clarify padding-bottom in overflow content`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-overflow-3] Clarify padding-bottom in overflow content<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/129<br>
&lt;dael> iank_: Introduction for this<br>
&lt;dael> iank_: Broadly we have been investigating scrollable overflow problems in blink. Lot of inconcsitent tests and inconsistent impl.<br>
&lt;dael> iank_: Including child margin plus scollable padding is what devs want we believe. Inconsistent between layouts and directions<br>
&lt;dael> iank_: 2 calculations. You take post tranform rectangle of child and add to scrollable. This is interop. Second is this issue. Take pre-transform rectangle and add it inflow bounds. Use that to determine where padding edge goes.<br>
&lt;dael> iank_: We think the model works. How webcompat is it is the question.<br>
&lt;dael> iank_: Think we should aim for what webdevs want but stop when web incompat. Prepared to slowly switch on various behaviors to get closer and closer. May hit a case where cna't go further due to compat.<br>
&lt;dael> fantasai: Totally in favor. Great to get to where authors want. Less likely to have problems with newer layouts flexbox and grid. more problems with older like block where trying not to add scrollbars when not necessary. Triggering when scrollbars appear is where will find problems<br>
&lt;dael> iank_: That's where we expect. We're going to do this slowly over 3-4 months and can report back success. For block in inline direction if there weren't going to be scrollbars previously we may not add padding but if there would be we add padding. Might end up with that which is a bit strange.<br>
&lt;dael> Rossen_: Sounds like a good proposal. Should we resolve and think about block more?<br>
&lt;dael> fantasai: I think we resolved on flex and grid<br>
&lt;dael> Rossen_: I think so too. Don't want to hold them waiting on block?<br>
&lt;dael> iank_: If we agree on direction we can report back on each step what was not web-compat. We'll start with flex probably. Report back. DO resolution on broad model now and web compat resolutions later maybe<br>
&lt;fantasai> current spec - https://www.w3.org/TR/css-overflow-3/#scrollable<br>
&lt;dael> Rossen_: Prop is for flexbox and grid? Want to make sure I'm going for right resolution<br>
&lt;dael> fantasai: Spec requires this for flex and grid, optional for block with an issue about web compat<br>
&lt;dael> iank_: Leave as is and in a few months I can come back with web compat data.<br>
&lt;dael> iank_: Tentative agreement we want to go that direction is good<br>
&lt;dael> florian: sgtm. We've been blocked on web compat data so let's get the data.<br>
&lt;dael> Rossen_: Then this is everything for today<br>

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 September 2020 17:02:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:17 UTC