314387 - Changes to custom page size of current page size are ignored

Status: RESOLVED INCOMPLETE

(Firefox :: Settings UI, defect)

Description

[Trey Harris]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051025 Firefox/1.5

Changes to custom paper sizes are ignored until you change to a different paper size and back again.

Reproducible: Always

Steps to Reproduce:
1. In Page Setup, create a custom page size, and save it.
2. Print (or print preview) a page.
3. Enter page setup again, edit the custom page size, and change a margin dramatically (so the cosmetic difference will be obvious).  Then save it.
4. Click OK.
5. Print (or print preview) again.  The new margin setting will not have taken effect.
6. Go back to page setup, change to some other paper size, click OK, then enter page setup again, and go back to the custom paper size.
7. Print (or preview) again.  Now, the new margin setting will have taken effect.
Actual Results:  
At step 5, the margin changes were not reflected in the output.

Expected Results:  
At step 5, the margin changes should have been reflected already.

Comment 1

[Micha³ Nowak]

This seems to be the same bug, description follows.

UA: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8) Gecko/20051111 Firefox/1.5


When printing page on different printer than previously, firefox uses page settings (mainly paper size) from previous job, not from currently selected printer.

In my webapp there's need to print address list on A4 page on laser printer and then series of address labels on 4x5 cm labels on Avery TTX450 printer.
After printing A4 page and changing printer to Avery, printer spits out not desired 1 page / 1 label but 1 page / 7 labels, which is rougly A4 height. Next printing immediately following the fault one on the same printer is correct.

This is not happening in "the other" browser, which has some other issues with printing though.

This behaviour is the same beginning from at least firefox 1.0 (haven't used it before 1.0).

Comment 2

[Tyler Downer [He/Him]]

This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.