1401469 - mega.nz insufficient buffer to decrypt data (not use FileSystem API in Firefox)

Status: REOPENED

(Web Compatibility :: Site Reports, defect, P2)

Description

[mdew]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20170919214925

Steps to reproduce:

Attempt to download a large file (Windows 10 insider build iso)

https://mega.nz/#!8QFxVDwS!2jdXw7OPVtgl_Ij2Xa1sg9tp2o-4EzXqVznMH4qlh58

De-select the option "Desktop App"


Actual results:

"Unfortunately, Firefox has an insufficient buffer to decrypt data in the browser, and we recommend you to install the MEGA desktop app to download large files (or use Chrome)"


Expected results:

Able to download/decrypt large files in files in Firefox

Comment 1

[YF (Yang)]

Chrome ask "Store files on this device".

https://superuser.com/questions/1190803/website-wants-to-store-files-on-this-device-chrome


Bug 1265767.

Comment 2

[Marco Castelluccio [:marco]]

What is the size limitation of our API? Would it be feasible to relax the limit if the user accepts a prompt?

Comment 3

[Andrea Marchesini [:baku]]

Firefox implements the Entries API: https://wicg.github.io/entries-api/
Chrome implements something that is currently deprecated: a full file system API: https://www.w3.org/TR/file-system-api/ 
From the fileSystem API description: "Work on this document has been discontinued and it should not be referenced or used as a basis for implementation."

Last time we spoke with chrome developers, they wanted to remove their file system API and switch to the entries API.
This seems not be true yet.

Comment 4

[Marco Castelluccio [:marco]]

Should we try to contact Mega and ask them to use the Entries API?

Comment 5

[Mike Taylor [:miketaylr]]

It's worth a shot, I guess. At least to start a conversation. Adam, could you try to get in touch with Mega? thanks.

Comment 6

[Adam Stevenson [:adamopenweb]]

Sounds good. We have another bug on webcompat.com for this as well.

Comment 7

[Adam Stevenson [:adamopenweb]]

Mega is on Github, along with some employees. I've reached out to them in the other bug report on Github.

Comment 8

[Masatoshi Kimura [:emk]]

Entries API has no ability to store files on local disks. I don't think it is useful to mega.nz.

Comment 9

[Andrea Marchesini [:baku]]

(In reply to Masatoshi Kimura [:emk] from comment #8)
> Entries API has no ability to store files on local disks. I don't think it
> is useful to mega.nz.

https://wicg.github.io/entries-api/ Entries API doesn't have such functionality. That is a chrome only API, deprecated btw.
We can consider the idea of extending Entries API, but so far, mega.nz is using something not part of the spec.

Comment 10

[Andrea Marchesini [:baku]]

See https://www.html5rocks.com/en/tutorials/file/filesystem/ and http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0010.html

Comment 11

[Masatoshi Kimura [:emk]]

What API should we propose to mega.nz, after all?  This bug will not be actionable without a concreate API available from the web.

Comment 12

[Masatoshi Kimura [:emk]]

Removing [sitewait] because we have no API to propose (yet).

Comment 13

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 14

[sphakka]

Workaround: use `megatools` https://github.com/megous/megatools in the meanwhile :-)

Comment 17

[Oana Arbuzov [:oanaarbuzov]]

Unfortunately the files from the provided links are no longer available.
https://mega.nz/#!8QFxVDwS!2jdXw7OPVtgl_Ij2Xa1sg9tp2o-4EzXqVznMH4qlh58
https://mega.nz/#!N5wnBAiI!zMSttFAuDy4UZ1x1ulaZstmsPb_zTASXI7ZiYk9I5eA

https://prnt.sc/vlhl6b

I've uploaded a file on my account, copied the link, and I was able to start downloading it (2.5Gb) without any issues.

Tested with:
Browser / Version: Firefox Nightly 85.0a1 (2020-11-17)
Operating System: Windows 10 Pro

mdew can you still reproduce it on your side?

Comment 18

[Elhem Enohpi]

The bug is not resolved. The file size needed to trigger it is in my experience above about 6 GB. I don't have a link to provide, sorry. Oana, your test isn't valid, can you please re-open the bug? Thanks.

Comment 19

[Oana Arbuzov [:oanaarbuzov]]

Thanks Elhem, I will reopen the issue.

Comment 20

[Raul Bucata]

As seen in previous comments, a file above 6GB is needed to be uploaded. We do not have such a file, unfortunately.

Reporter, could you please provide a link that might fulfill these requirements?

Comment 21

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:denschub, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 22

[Dennis Schubert [:denschub]]

Closing as incomplete as per Comment 20. We can always reopen this bug in the future if new information arises.

Comment 23

[Calin Tanase]

We have received a new bug report on github where the user is unable to download his 7GB file on Firefox.

Limitations for Firefox users, see also: https://help.mega.io/files-folders/transfers/browser-download-limitations

Comment 25

[BugBot [:suhaib / :marco/ :calixte]]

The severity field for this bug is set to S3. However, this bug has a P1 WebCompat priority.
:ksenia, could you consider increasing the severity of this web compatibility bug?

For more information, please visit BugBot documentation.

Comment 26

[Dennis Schubert [:denschub]]

(Re-calculating the fields based on the current triage addon version)

Comment 27

[Randell Jesup [:jesup] (needinfo me)]

We do support OPFS, which allows writing files directly, but not to anywhere in the filesystem. Photoshop for example uses this. This might work for mega.nz. This would be outreach. Dennis, can you see if that would work for them?

We will not be supporting the Filesystem API.
Moving from affects:all to affects:some because mega.nz will only limit us if the file is over 7GB for 64-bit systems (1GB for 32-bit).

Comment 28

[Dennis Schubert [:denschub]]

(In reply to Randell Jesup [:jesup] (needinfo me) from comment #27)

Dennis, can you see if that would work for them?

I wish, but we don't have active contacts. Adam tried reaching out to them on GitHub and by sending some emails and DMs, but to no avail. We should try again, though, it's been a while. Putting this back into the needs-contact pile.