476502 - Menu items disabled on print dialog display, enabled again after print preview

Status: RESOLVED DUPLICATE of bug 458054

(Firefox :: Menus, defect)

Description

[andrewn]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6

After visiting the print dialog and selecting cancel, the following menu items are disabled on the File menu: Close, Save Page As, Send Link, Page Setup, and Print.

To get them enabled again, it is necessary to access the print dialog (by pressing Command+P - as the menu item will not work) and clicking the Preview button.

This has been around for some time, but I figured it would be noticed and fixed.  I only seem to have this problem on OS X - I have not noticed it on Linux.

When I went to report this bug I thought it was just the Print and Page setup menu items disabled, but now I see it is all of those listed above.  I'm not sure if that is new in this latest beta or not, but the Print and Page setup were definitely exhibiting this behavior in the last full release as well.



Reproducible: Always

Steps to Reproduce:
1. Click File/Print.
2. Select Cancel.
3. View the file menu.
Actual Results:  
The following menu items are disabled on the File menu: Close, Save Page As, Send Link, Page Setup, and Print.


Expected Results:  
Nothing

Default settings.  MacBook Pro OS X 10.5.6 (but I am quite certain this happened on 10.5.x)

Comment 1

[andrewn]

The menu items are also disabled if you enter the page setup dialog, change some settings, and click okay, or even if you simply enter the page setup dialog and click cancel.  Print preview still enables the menu items again.

Comment 2

[Tyler Downer [He/Him]]

This WFM with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090202 Minefield/3.2a1pre. Have you created a new profile and tried there?

Comment 3

[andrewn]

I just created a brand new profile and experienced the same behaviour.

I see that you are running on Windows - I noted already that I have not seen this behaviour on Linux and therefore assume it is a Mac OS X specific issue.