- From: Morten Stenshorne <notifications@github.com>
- Date: Thu, 24 Jul 2025 02:27:40 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 July 2025 09:27:44 UTC
mstensho left a comment (w3ctag/design-reviews#1115) Actually, yes, things have been moving since I filed this. If you read from https://github.com/w3c/csswg-drafts/issues/11395#issuecomment-3028315523 ... I just updated the explainer with a note regarding this, since it's definitely worth mentioning there as well. Re-using `safe-area-inset-*` was my initial idea, actually. It's not a perfect fit, though, since we can only reliably provide one and the same value for each of the four edges. Additionally, https://drafts.csswg.org/css-env-1/#safe-area-insets says: > For rectangular displays, these must all be zero But anyway, I think we should explore the keyword-based proposal from Mozilla (one descriptor / property) for page and page margin contexts to tell whether used margins should be clamped to the printable area (new) or not (current behavior). -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1115#issuecomment-3112734208 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1115/3112734208@github.com>
Received on Thursday, 24 July 2025 09:27:44 UTC