155558 - [10.1] Can't enter page range in Print dialog

Status: VERIFIED WONTFIX

(Camino Graveyard :: Printing, defect)

Description

[Albert Kammerer]

I am using Mac OS 10.1.5 and Navigator build 2 July. Attempting to print just a
part of a page always results in the entire document being printed. You can
select print page 2 of 3, but all three pages will always print. I am also using
an HP DeskJet 932c.

Comment 1

[Greg K.]

Albert, I presume this is also Chimera-specific, and that it doesn't happen in
Mozilla. Is that correct?

Does this also occur using only print preview PDF creation?

Comment 2

[Albert Kammerer]

This is Chimera-specific and you can see the effects of it using the "Preview"
button in the print dialog box. Mozilla previews just the selected pages and
Chimera previews them all.

Comment 3

[Greg K.]

Confirmed using Chimera/20020708. Chimera fails to restrict print preview to
indicated page range.

Comment 4

[Simon Fraser [no longer active]]

->conrad

Comment 5

[Conrad Carlen (not reading bugmail)]

I can't even enter a page range in the print dialog. The page range fields are
dead to keyboard input.

Comment 6

[Simon Fraser [no longer active]]

This works fine for me on 10.2; i can enter into the page range fields, and
preview to see just the pages chosen.

Comment 7

[Conrad Carlen (not reading bugmail)]

> This works fine for me on 10.2

Yes. It's true :-)

I would imagine it's still a problem on 10.1. The thing that's curious is that,
for me on 10.1, the problem was not being able to type in the page number
fields. Nobody on the bug before comment 4 mentioned that, which is hard to
believe. Is it possible that, as of 2002-07-10, you could type in the dialog but
the printing code failed to use the values? But then, after 07-10, we lost the
ability to type in the dialog?  

Comment 8

[sairuh (rarely reading bugmail)]

going thru some printing tests: still a problem on 10.2.1, even though as in
comment 6 i can at least select the pages in the print dlg.

Comment 9

[Conrad Carlen (not reading bugmail)]

Can you give a URL and some more info? In basic testing, WFM.

Comment 10

[sairuh (rarely reading bugmail)]

i just retried this on 10.2.1...and it works now.

will test this out on 10.1.5 in a bit.

Comment 11

[sairuh (rarely reading bugmail)]

okay, using today's build on 10.1.5, i'm seeing what conrad saw in comment 5: i
cannot change the range inputs from something other than page 1 to page 1.

interestingly, if i select the "page 1 to page 1" setting, only the 1st page is
printed (as expected).

Comment 12

[ender_mb]

On OS 10.1.5 with Chimera build 2003010706 the 'copies' and range text fields
still don't respond to keyboard input...

Comment 13

[Josh Aas]

What is the position on whether or not Camino still supports Mac OS X 10.1.5? If
we don't (which I don't think we should for various reasons), then this bug is a
moot point.

Comment 14

[Chris Casciano]

*** Bug 196345 has been marked as a duplicate of this bug. ***

Comment 15

[Conrad Carlen (not reading bugmail)]

*** Bug 187630 has been marked as a duplicate of this bug. ***

Comment 16

[Stuart Morgan]

Updating summary to use [10.1] to make it easier to find with the other 10.1
bugs, and taking.

I'm almost positive that this bug is caused by the same thing causing bug
163830. If the location bar has focus when Print (or Page Setup) is invoked, the
location bar will actually recieve the keypresses that should go to the Print
fields--which is why the fields can't be changed. The behavior of these
keypresses is the same as described in bug 163830 (most keys work, but delete
does nothing and forward delete/arrow keys move the cursor forward without
actually creating spaces).

Comment 17

[Stuart Morgan]

In 10.1, the frontmost browser window is not getting either a didResignKey or
didResignMain when the print panel is displayed. In 10.3, both occur.

I'm still at a loss for why. Any guesses? Thoughts on hacks, ugly or otherwise,
to get a handle for the print panel so that we can force it to be key/main?

Comment 18

[Stuart Morgan]

Giving my bugs back to pink.

Comment 19

[Blixman]

cannot replicate (i.e. works fine).

10.1.5, 0.8.2rc

Comment 20

[Josh Aas]

We don't support 10.1.x any more anyway, so closing this bug.

Comment 21

[Stuart Morgan]

*** Bug 337788 has been marked as a duplicate of this bug. ***