- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Sat, 30 Aug 2025 19:33:12 +0000
- To: public-css-archive@w3.org
@bfgeek: > Its important to note this was done for the popover type usecase - e.g. it looks bad if you unnecessarily flip back as scrolling back up. @tuankiet65: > I suppose web developers will like Safari's behavior more (position is more predictable) but web consumers will like Chrome's behavior more (layout stability, stuff don't randomly jump around). @kizu: > the behavior that was implemented in Safari is what many authors expect. Given @kizu's [findings](https://github.com/w3c/csswg-drafts/issues/12682#issuecomment-3239346226), my guess is that the majority of authors _and_ users rather expect Safari's behavior. I'd even say it also makes sense for the popover use case outlined by @bfgeek to prefer the position stability over layout stability, as it reduces cognitive load when you can expect the popover to always be at the same position except when it doesn't fit. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12682#issuecomment-3239499288 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 30 August 2025 19:33:13 UTC