- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Fri, 11 Jul 2025 19:30:41 +0000
- To: public-css-archive@w3.org
Right, we had to balance different types of badness here. When the CB is relatively small, with space around it, the specified default behavior (which shifts the positioned element to keep it within the CB) looks bad - it can cause overlap with the anchor while appearing to avoid using the plentiful space surrounding it. But when the CB is the size of the screen, the specified default behavior is *exactly what you want* - it avoids the positioned element going off-screen (either into the unscrollable area, or making the page pop a horizontal scrollbar). Similarly if the CB is small but a scroller. We judged that fixpos and top-layer anchor-pos (and abspos that doesn't have a containing block, so it hits the root), where the CB is the width of the screen, was going to be a very common case, and the failure mode of `unsafe` was somewhat worse in this case, so we biased towards safety here (shifting to keep it in the CB). -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12466#issuecomment-3063523106 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 July 2025 19:30:42 UTC