w3c / w3c/csswg-drafts

[css-page] Can blank pages be named pages and how?

Open
#7,334 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-page-3
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

In PDFreactor we have implemented both blank pages and named pages. Currently our blank pages never have a name.
After customer feedback we are now looking into changing this. Our current plan is for blank pages to have the same name as the previous page.
However, we were not able to determine the actually expected behavior from the specification.

For example, what would be the background colors of page 2 and 4 in the following sample?

<html>
    <head>
        <style>
            p { break-after: right }
            #a { page: pagea }
            #b { page: pageb }
            @page pagea { background-color: lightblue }
            @page pageb { background-color: yellow }
            @page:blank { @top-left { content: "blank page: what color?" } }
        </style>
    </head>
    <body>
        <section id="a">
            <p>page 1: lightblue</p>
            <p>page 3: lightblue</p>
        </section>
        <section id="b">
            <p>page 5: yellow</p>
        </section>
    </body>
</html>

If you could clarify this issue we'd appreciate it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CSS page and blank-page specification sections, then compare their rules with the HTML/CSS example in this issue. Determine whether blank pages inherit a page name and which background colors and margin content pages 2 and 4 should use. Done means the specification's expected behavior is clearly resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation, web-dev
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.