- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Jun 2021 17:01:39 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Scrollable overflow`. <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Scrollable overflow<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/4791<br> <fantasai> fantasai: Seem to have weird but interoperable behavior here, question was should we spec it<br> <fantasai> iank_: not so weird, we compute the "inflow" bounds<br> <fantasai> iank_: ...<br> <fantasai> iank_: If you add a transform to the item and move it outside the scrollable area<br> <fantasai> iank_: all browsers transform out<br> <fantasai> iank_: if something is zero area, it doesn't itself contribute, but it might contribute to "infow bounds"<br> <fantasai> fantasai: ???<br> <fantasai> iank_: If you have something like a grid area, that's where we determine where to put the "padding" to contribute to overflow<br> <fantasai> iank_: Here it's the body element contributing to the scrollable area<br> <fantasai> fantasai: OK, so need to set body to zero to test correctly and issue is invalid?<br> <fantasai> iank_: question of adding to overflow is just if it's empty<br> <fantasai> fantasai: Actually, there is an issue, but it's just that if the border area is empty, we need to exclude from the scrollable area<br> <fantasai> iank_: yea, but also this other thing<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4791#issuecomment-862552475 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 June 2021 17:02:45 UTC