Skip to content
This repository was archived by the owner on Feb 24, 2026. It is now read-only.
This repository was archived by the owner on Feb 24, 2026. It is now read-only.

Split in two? Office printing needs are far removed from publishing #4

@cmawhorter

Description

@cmawhorter

Every five years or so I end up trying to find a solution to a printing problem: how to make a browser not print the default header/footer garbage. Something that sounds like it should be easily possible but is not at all.

The vast majority of web pages being printed will be from someone in an office printing something for someone else in that office. I'd like to throw out this suggestion -- Divide this proposal in two:

  1. Cross-browser/cross-OS normalization of what is expected out of the browser for printing (right now it's a mess based on an abandoned document from 2013 I think?)
  2. All the fancy desktop publishing stuff

The 1 stuff is definitely not trivial to solve, but I'd hate to have to wait for 2 to solve what are very basic/common problems impacting lots of people every day.

(Maybe this isn't the right place, but I couldn't find a better one)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions