OK button on Open with/Save To dialog from History grayed on if history double clicked

VERIFIED EXPIRED

Status

()

--
minor
VERIFIED EXPIRED
14 years ago
10 years ago

People

(Reporter: weiserware, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

If you have a history item which is a direct link to a file, and you
double-click the history item, two Open with/Save To dialogs are displayed and
both have the OK button disabled (including the dialog that has the focus). 
When you activate the dialog in the background, the OK button on that dialog is
enabled.  When you activate what was previously the foreground dialog, that OK
button gets enabled.

Reproducible: Always

Steps to Reproduce:
1. Download a file from the location bar so you get a direct link to the file in
your history.
2. Double-click the history item for that file.

Actual Results:  
As described above.

Expected Results:  
OK button on both dialogs should be enabled.  I have never seen any other apps
on Windows where the OK button is conditionally disabled.

May be related to bug 284579 which talks about dialogs without focus having the
OK button disabled.

Comment 1

14 years ago
Reporter: Look at bug 264492 and see if you think this is a duplicate of that. 
I'm not sure enough to do it right now.
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> Reporter: Look at bug 264492 and see if you think this is a duplicate of that. 
> I'm not sure enough to do it right now.

I don't think its the same as that bug.  I don't have any of the file
association problems reported in 264492 (my OK button is always enabled when
downloading files from links).  This bug (292924) seems to be more focus related.

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED

Updated

10 years ago
Component: History → Bookmarks & History
QA Contact: history → bookmarks

Updated

10 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.