Closed Bug 382987 Opened 13 years ago Closed 12 years ago
WMV file auto download is not remembered if "Do this automatically for files like this for now on" is checked
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20070515 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20070515 Firefox/184.108.40.206 When I click on a movie file link of WMV type the "Opening <file URL>" window pops up. Somewhere in that window there's a check box "Do this automatically for files like this for now on". I check that box to avoid seeing this window again and begin downloading by clicking OK. This setting doesn't seem to work. If I click on the same link again, or other link with WMV extension the Opening window pops up again. This seems to work for any other file type but this one. So hopefully you'll be able to fix this. PS. There's also one more thing I need to tell you. You have a really complicated way to report bugs. I spent over 15 minutes just to get to this point. Plus all these questions -- they are too hard for regular Joe to answer. I'm sure you'd get a far better feedback if you simply let people explain bugs in a plain text window. Just my opinion. Don't make things complicated (like Microsoft :) Reproducible: Always Steps to Reproduce: 1.Go to any link referring to WMV file 2.Click on it to download, check the box to remember the setting, hit OK 3.Try again next time
i can confirm this on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007070917 Minefield/3.0a7pre
this is probably fixed now, i can no more reproduce on Trunk reporter: could you try the latest Trunk nightly build and report your experience on this problem?
Resolving old UNCONFIRMED Download Manager bugs as INCOMPLETE. If you still see this issue, please reopen. To mark all these bug changes as read, filter on ONOMATOPOEIA.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Still see it with .torrent files on FF 3.0.6.
You need to log in before you can comment on or make changes to this bug.