- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jan 2025 12:15:35 +0000
- To: public-css-archive@w3.org
> [@flackr](https://github.com/flackr) Would it make sense to redefine the current safe area insets to be the maximum safe area inset, rather than introducing a new set of variables for it, so that it affects existing content? That would be a breaking change and defeat the purpose of these variables. I took Rob’s proposal [for a spin](https://cdpn.io/pen/debug/wBwExjB/e642977569751476fbc6a85eed301270) and while it did take a while to click – as in: the footer gets taller but it all works out because you pull it back down – it’s a nice solution that would allow a translate-only adjustment by UAs as the viewport grows/shrinks. _(Elements that use `padding-bottom: env(safe-area-inset-bottom, 0px);` would not get the benefits, which could be part of DevRel guidance around this)_ -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11019#issuecomment-2604566418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 January 2025 12:15:36 UTC