Re: [csswg-drafts] [css-page] Expose unprintable areas via CSS (#11395)

1) `clamp` and `add` seem fine, sure. :) (describing in-what-way the safe margin gets applied as a modifier to the specified `margin` values)

2) Agreed, I think Chrome is buggy on this; I recall from previous testing that `size: [...]` does successfully parse in regular style rules in Chrome, and that that's a bug (and may cause you some trouble if a `size` shorthand for `width, height` is eventually added as proposed in #820).

> So... well... let page-margin-safety be a property instead, one that only applies in page and margin contexts? 😄

I'm not sure that's really meaningful... (i.e. a "property" that's visible to @supports but somehow only usable as a descriptor).

We could, of course, conceivably create some related "dummy" property that's technically valid in CSS declarations but has no effect, which only exists to let us do `@supports()` feature-detection for that property as a way to find out if the descriptor is supported.  But that feels pretty hacky.

> Or introduce a shorthand "descriptor" that sets both page-margin-safety and margins?

That feels less hacky and more robust, yeah.  The shorthand might want to be called something like `page-safe-margin` (ending with "margin") to make it clear that it is primarily a margin plus some flags.  And if that naming makes sense, then maybe the longhand here might want to be an extended version of that name --  e.g. `page-safe-margin-mode`, though maybe "mode" could be a better word.

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11395#issuecomment-3282479035 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 11 September 2025 20:12:40 UTC