- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Nov 2022 23:23:54 +0000
- To: public-css-archive@w3.org
> However, if we follow the behavior of 1, then both fallback positions will overflow the inset-modified containing block (because top/bottom will evaluate to something around 1000vh, making the available space empty). Then we always end up using the last fallback position. For the scroll behaviour - wouldn't we test if the element is overflowing the contianing block (similar to sticky-pos). E.g. that part of the calculation wouldn't depend on the inset-modified containing-block? -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8059#issuecomment-1320646531 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 November 2022 23:23:56 UTC