270307 - can't click OK after selecting file handler

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Florin Andrei]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

I browse to the URL indicated above. I go to Synths / Ion and click on Quick
Start Manual. A small window pops up, asking me what to do with the file. The OK
button is greyed out.
I select "Open with", then in the drop-down i select "Other". I browse the
filesystem to /usr/bin and select "acroread" then click on Open.
The problem is, after selecting /usr/bin/acroread in the "Open with" option, the
OK button is still greyed out! No matter what i do, it's still grey and
unclickable. This is very frustrating.

Please don't grey out the button anymore. Thank you.

Reproducible: Always
Steps to Reproduce:
1.go to indicated URL and click on Quick Start Manual
2.select /usr/bin/acroread
3.

Actual Results:  
The OK button is grey and i cannot open the file in acroread

Expected Results:  
The OK button should be clickable and allow me to open the document in acroread.

The URL that demonstrates this problem is just one among many that show this
behaviour.
Moreover, it's not limited to the example i'm describing (opening PDF files in
acroread) but with pretty much any file type and file handler.

I think, greying out the button is a good idea gone bad. I can see the reasoning
behind it (prevent users from making silly mistakes) but it only takes one bug
like this one to turn a useful feature around into an annoying problem.

Please let the users "make mistakes". Please don't grey out buttons
automatically anymore.

Comment 1

[Florin Andrei]

Attachment: here's a screenshot showing the problem

The OK button is grey and unclickable, and no amount of tweaking can make it
active again.

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.