Open Bug 142085 Opened 22 years ago Updated 2 years ago

Preemptive printing mode

Categories

(Core :: Printing: Output, enhancement, P3)

enhancement

Tracking

()

Future

People

(Reporter: phil, Unassigned)

References

Details

Mozilla 1.0 Release Candidate 1
Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.0rc1) Gecko/20020417

When printing a lot of pages the printer only processes one print job for a
"long" time and other users have to wait. In multiuser / network environments
this can be very annoying. And the OS only allows to specify the priority of the
job but can't split the job. It should be built in every OS - but in the
meanwhile mozilla could be ahead of the pack by providing this cool new feature:
"Preemtion printing mode" where the whole job is split up in a number of jobs.
let the user choose:
o one printjob for every page
o split up in xx KB parts
o ...
Confirming RFE...
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Status: NEW → ASSIGNED
Priority: -- → P2
when configuring:

o "split up in xx KB parts" one page would be the granularity - so one page
can't be split up - just to be not misunderstood :-)
Bulk moving P1-P5 un-milestoned bugs to future. 
Target Milestone: --- → Future
Blocks: 125824
Summary: Preemtion printing mode → Preemptive printing mode
I can't see that being useful to the average user or even sub-average. (I don't even see it being the responsibility of the application)

Is this amenable to being provided by an extension?
Assignee: rods → printing
Status: ASSIGNED → NEW
QA Contact: sujay
Assignee: printing → nobody
QA Contact: printing
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.