Skip to content

[css-page-3] Proposed spec changes for safe printable insets. #11395#13190

Open
mstensho wants to merge 2 commits intow3c:mainfrom
mstensho:mstensho/safe-printable-inset
Open

[css-page-3] Proposed spec changes for safe printable insets. #11395#13190
mstensho wants to merge 2 commits intow3c:mainfrom
mstensho:mstensho/safe-printable-inset

Conversation

@mstensho
Copy link
Contributor

@mstensho mstensho commented Dec 8, 2025

@mstensho mstensho changed the title Proposed spec changes for safe printable insets. [css-page-3] Proposed spec changes for safe printable insets. #11395 Dec 8, 2025
@lilles lilles requested a review from fantasai December 18, 2025 07:27
@mstensho mstensho marked this pull request as ready for review December 19, 2025 09:44
@mstensho
Copy link
Contributor Author

mstensho commented Jan 2, 2026

@fantasai Does this look okay?

@faceless2
Copy link

faceless2 commented Jan 15, 2026

	Name: page-margin-safety
	For: @page
	Value: none | clamp | add
	Initial: auto
	Computed Value: as specified

Based on the example four paragraphs after that clause, wouldn't For be "page margin boxes" not @page?

@mstensho
Copy link
Contributor Author

mstensho commented Jan 15, 2026

	Name: page-margin-safety
	For: @page
	Value: none | clamp | add
	Initial: auto
	Computed Value: as specified

Based on the example four paragraphs after that clause, wouldn't For be "page margin boxes" not @page?

It's actually for both @page and @page margin boxes. How do I express that in this language?

@SebastianZ
Copy link
Contributor

	Name: page-margin-safety
	For: @page
	Value: none | clamp | add
	Initial: auto
	Computed Value: as specified

Based on the example four paragraphs after that clause, wouldn't For be "page margin boxes" not @page?

It's actually for both @page and @page margin boxes. How do I express that in this language?

@tabatkins Is it possible to define a descriptor for multiple at-rules at once? Or should they be referenced differently in that case?

Sebastian

Issue for multiple at-rules not supported by bikeshed.
@mstensho
Copy link
Contributor Author

I discussed this with @tabatkins , and bikeshed currently doesn't support specifying multiple at-rules here. I pointed this out in an ISSUE in the spec instead, and listed all the additional at-rules where this applies.

@mstensho
Copy link
Contributor Author

Any more feedback? Ready to land?

mstensho added a commit to web-platform-tests/wpt that referenced this pull request Feb 25, 2026
For print reftests, check <meta name="safe-printable-inset"> to simulate
an unprintable region along the paper edges. The `content` attribute
takes a non-negative number, which is the safe printable inset specified
in centimeters.

Only implemented for executorwebdriver.

Spec discussion: w3c/csswg-drafts#11395
Spec change: w3c/csswg-drafts#13190
RFC: web-platform-tests/rfcs#233

For background, see https://drafts.csswg.org/css-page-3/#printable-area
mstensho added a commit to mstensho/webdriver that referenced this pull request Feb 25, 2026
This is for testing the `page-margin-safety` descriptor in `@page` and
page margin box contexts.

Spec discussion: w3c/csswg-drafts#11395
Spec change: w3c/csswg-drafts#13190
RFC: web-platform-tests/rfcs#233

wptrunner and webdriver code changes:
web-platform-tests/wpt#58030
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants