- From: Morten Stenshorne via GitHub <noreply@w3.org>
- Date: Mon, 07 Jul 2025 07:41:23 +0000
- To: public-css-archive@w3.org
Interesting approach. I too am not sure if we would need ways to specify this individually for each side, if we go down this path. True, this is less expressive than the `env()` approach, which would allow for (presumably) silly things like `flex-basis: env(safe-printable-inset)`. Using `env(safe-printable-inset)` IS silly as long as we're not dealing with something that's flush with the page area edges. Using it for widths and height is always silly. But I guess that's environment variables for you. As if e.g. `width: env(safe-area-inset-top)` makes a lot of sense... Not sure about `minimum` vs `balanced`. Since we have no control over what the printer does regarding rotating the output, and whether it's the short or the long edge that's fed first, there's no meaningful individual safe inset. -- GitHub Notification of comment by mstensho Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11395#issuecomment-3043826996 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 July 2025 07:41:24 UTC