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

This seems reasonable.  I have two minor concerns, though I don't have concrete suggestions for how to address them:

(1) bikeshedding the value names:  it's a bit odd that `clamp` and `additive` are different parts of speech (`clamp` is a verb or noun, whereas `additive` is an adjective).

(2) Is it possible to feature-detect this so that web developers can offer "just-in-case" graceful fallback, e.g. a `0.5in` presumed-to-be-generally-safe margin? If not, I'm a little uneasy about how content-using-this-feature will render in UAs that lack support for it.  e.g. if you do the aforementioned obvious thing of setting `margin:0` with a safe-inset applied via this new descriptor, then UAs that lack support for this new descriptor will end up just seeing `margin:0`, which will probably lead to clipping on all real printers. So it would be safer if it were possible to guard the `margin:0` declaration in a some sort of opt-in snippet where the web developer knows that the new descriptor is supported/applied. (Intuitively I'd expect to be able to use `@supports` but I wasn't able to get that to work, wrapping the insides or outsides of a `@page {...}` rule.  If that can be made to work, that's great; but so far I'm failing at getting it to work.)

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


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

Received on Wednesday, 10 September 2025 22:59:03 UTC