- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 16:25:06 +0000
- To: public-css-archive@w3.org
The spec is fine wrt. to this IMO. The margins aren't directly added to the scrollable overflow - rather the margins are affecting the inflow-bounds: "Additional padding added to the end-side of the scrollable overflow rectangle as necessary to enable a scroll position that satisfies the requirements of place-content: end alignment." The test there *isn't* testing at we add the margins *directly* to the scrollable overflow. There is an open question if we need the to add margins (directly) at all now, from feedback we've received about the "additional padding" change it isn't, and this matches developer expectations. Currently Gecko/WebKit aren't actually following the spec here adding margins in all cases for example: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=11464 (If margins were being added directly there'd be overflow in that test). (Gecko is doing this in a somewhat broken manner for block containers however, e.g. when margin-collapsing is present - https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=11465 ) Instead Gecko/WebKit are only doing this if it is a flex/grid container is a "scrollable container" as well. The difference here is super sutble - but likely isn't needed anymore since we perform the "additional padding" now. Thoughts? Ian -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8660#issuecomment-1490587450 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 March 2023 16:25:08 UTC