Batch-aware page range syntax for mixed duplex/simplex print jobs

[ebiofuel]

Problem Statement

Firefox’s current print dialog treats a print job as a single, uniform configuration (duplex, simplex, etc.).

For real-world document workflows, especially contracts and technical documents, this is limiting. Users frequently need to:

• Print sections duplex (main document)

• Insert specific pages as simplex (signature pages, inserts)

• Continue duplex afterward (appendices)

Currently, this requires:

• Multiple manual print jobs

• Reconfiguring settings between each job

• Increased risk of error (wrong mode, page misalignment)

This is inefficient and not scalable for repeated workflows.

Proposed Solution

Introduce syntax-based batch printing within the existing Custom Pages field, allowing Firefox to parse and split a single print request into multiple internally-managed sub-jobs.

Example Syntax

1-12d,12s,13-*d

Interpretation

Segment Meaning

1-12d	Pages 1–12 printed duplex
12s	Page 12 printed simplex (duplicate page)
13-*d	Pages 13 through end printed duplex

Syntax Specification (Proposed)

• , → separates print segments

• - → defines page range

• * → last page

• d → duplex

• s → simplex

Implementation Concept

Firefox would:

1. Parse the string into structured segments

2. Generate sequential print jobs with different settings

3. Dispatch them to the system print driver in order

This avoids requiring:

• Changes to printer firmware

• Changes to OS-level print APIs

Firefox acts as the orchestration layer.

Use Cases

1. Contract workflows (primary use case)

• Duplex document

• Single-sided signature pages

• Duplicate signature copies

2. Land management plans (my case)

• Main report (duplex)

• Signature pages (simplex, multiple copies)

• Appendix (duplex)

3. Legal / compliance documents

• Insert affidavit pages

• Controlled formatting requirements

This feature would significantly improve Firefox’s utility in professional environments where document control matters. The implementation is largely parser + job sequencing logic, making it relatively contained while offering high user value.

To be upfront, I used AI to help me draft this post, work on grammar, and standardize formatting. The idea is human.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.