#1046: safe-area-max-inset-* variables
Discussions
Log in to see TAG-private discussions.
Discussed
Feb 10, 2025 (See Github)
Xiaocheng: extentsion to safe area inset variables... e.g. on a non-rectangular screen... anything within that safe area will not be outside of the screen. The safe are inset is dynamic.. which causes layout instability. So they propose a safe area max. I don't see anything architectural ... any issues. This seems to be a straightforward. Nothing concerning here.
Dan: we should revisit at the plenary.
Comment by @xiaochengh Feb 12, 2025 (See Github)
We're happy with this. But please put this text you've written either in a separate explainer doc https://w3ctag.github.io/explainers/ or in the spec itself.
OpenedJan 30, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of safe-area-max-inset-* variables.
This proposal adds safe-area-max-inset-* variables that have the value of the max possible value of the safe-area-inset-* variables. This can be used to create a different effect (a bottom bar that slides) while still respecting the safe area insets and while remaining composited.
See further discussion on: https://github.com/w3c/csswg-drafts/issues/11019
This proposal builds upon the safe-area-inset variables specified here https://drafts.csswg.org/css-env-1/#safe-area-insets. The safe-area-inset variables can dynamically change based on the device, which can require relayout or in some cases jittery appearance. There are some efforts to be able to composite such changes, but it isn't easily possible in all cases. With that, we propose adding safe-area-max-inset-* set of properties that represent the maximum value that the safe-area-inset-* variables can take. These are static and do not change on the device, which allows developers to reliably use the variables to create smooth and fast effects like bottom-bars that slide down as the safe-area-inset-* changes (as an example).
Further details: