Closed Bug 1527399 Opened 5 years ago Closed 5 years ago

Not correct work function "Run automatically for all files of this type" Firefox 65

Categories

(Toolkit :: Downloads API, defect)

65 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 453455

People

(Reporter: veron.nv, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Actual results:

  1. The .torrent file does not open automatically when the torrent client is selected. A dialog box appears constantly, even if the corresponding checkbox is checked.
    Developers, please correct this bug. I am using Firefox 65 (x64), Windows 7 (x64).
    Test Link / Screenshot
    I also use Chrome 72 and there is no such problem, the torrent file is correctly transferred to the client.

As a temporary solution i use extension InlineDispositionV2, but it breaks the download files on other sites, so it is not suitable for permanent use.
I think this feature should work correctly by default without using additional extensions.

  1. Also this function becomes inaccessible for some files, for example .lua (https://cloud.mail.ru/public/ApT5/1bqegfEp7). I cannot check the box to download such file extensions without a dialog box.

Please make sure that 'any' file types are downloaded without an additional dialog box if the box is checked for "Run automatically for all files of this type".

(In reply to veron from comment #0)

InlineDispositionV2, but it breaks the download files on other sites

There are many such add-ons; use a different one. For example, Header Editor lets you create rules per-site. If you're looking for something simpler, then Bypass Forced Download lets you whitelist certain sites.

(https://cloud.mail.ru/public/ApT5/1bqegfEp7). I cannot check the box to download such file extensions without a dialog box.

The server sends Content-Type: application/octet-stream meaning the file type is unknown, so it's not possible to always perform an action for it. See bug 393029 and bug 417922. You can override the content type with the aforementioned Header Editor add-on.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Component: Untriaged → Downloads API
OS: Unspecified → All
Product: Firefox → Toolkit
Hardware: Unspecified → All
Resolution: --- → DUPLICATE

(In reply to Gingerbread Man from comment #1)

There are many such add-ons; use a different one. For example, Header Editor lets you create rules per-site. If you're looking for something simpler, then Bypass Forced Download lets you whitelist certain sites.

Why does the user need such difficulties? I do not understand this, and especially do not know English. Why does Google Chrome have no such problems, and Firefox creates them and does not want to fix them? I use Google Translate.

The server sends Content-Type: application/octet-stream meaning the file type is unknown, so it's not possible to always perform an action for it. See bug 393029 and bug 417922. You can override the content type with the aforementioned Header Editor add-on.

Therefore, I believe that this is a bug in Firefox browser, so this theme was created to solve this problem.
Why should I install various extensions when the browser should do this by default without them? Why in Google Chrome this moment works without problems and is on the convenience side for the user. Why is Firefox not meeting the user?

I tried to use "Bypass Forced Download", but I need to whitelist a lot of sites, this is very annoying, because sometimes the site may have a timer set between downloads, for example, on file sharing sites, so to find out that this site does not work on Firefox I have to first click on the download button, then I understand that it does not work, then I add to the white list, but I already have to wait for the next download after 30 minutes, because the site believes that I have already started downloading from this IP.
Firefox should know any type of file and, upon the user's request, automatically open it without an additional dialog box.

For 11 and 12 years you have not corrected these bugs (bug 393029, bug 417922, bug 453455) - this is a disaster! Why don't you strive for excellence?

You need to log in before you can comment on or make changes to this bug.