mega.nz insufficient buffer to decrypt data (not use FileSystem API in Firefox)
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(firefox92 affected, firefox113 affected)
People
(Reporter: mp3geek, Unassigned)
References
()
Details
(Keywords: parity-chrome, webcompat:site-wait, Whiteboard: [webcompat:needs-knowledgebase])
User Story
platform:windows,mac,linux impact:workflow-broken affects:all
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
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•6 years ago
|
||
What is the size limitation of our API? Would it be feasible to relax the limit if the user accepts a prompt?
Comment 3•6 years ago
|
||
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•6 years ago
|
||
Should we try to contact Mega and ask them to use the Entries API?
Comment 5•6 years ago
|
||
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•6 years ago
|
||
Sounds good. We have another bug on webcompat.com for this as well.
Comment 7•6 years ago
|
||
Mega is on Github, along with some employees. I've reached out to them in the other bug report on Github.
Comment 8•6 years ago
|
||
Entries API has no ability to store files on local disks. I don't think it is useful to mega.nz.
Comment 9•6 years ago
|
||
(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•6 years ago
|
||
See https://www.html5rocks.com/en/tutorials/file/filesystem/ and http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0010.html
Comment 11•6 years ago
|
||
What API should we propose to mega.nz, after all? This bug will not be actionable without a concreate API available from the web.
Updated•6 years ago
|
Comment 12•6 years ago
|
||
Removing [sitewait] because we have no API to propose (yet).
Comment 13•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Comment 14•6 years ago
|
||
Workaround: use `megatools` https://github.com/megous/megatools in the meanwhile :-)
Assignee | ||
Updated•5 years ago
|
Comment 17•4 years ago
|
||
Unfortunately the files from the provided links are no longer available.
https://mega.nz/#!8QFxVDwS!2jdXw7OPVtgl_Ij2Xa1sg9tp2o-4EzXqVznMH4qlh58
https://mega.nz/#!N5wnBAiI!zMSttFAuDy4UZ1x1ulaZstmsPb_zTASXI7ZiYk9I5eA
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•3 years ago
|
||
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•3 years ago
|
||
Thanks Elhem, I will reopen the issue.
Updated•3 years ago
|
Comment 20•2 years ago
|
||
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•2 years ago
|
||
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.
Updated•2 years ago
|
Comment 22•2 years ago
|
||
Closing as incomplete as per Comment 20. We can always reopen this bug in the future if new information arises.
Comment 23•1 year ago
|
||
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
Updated•15 days ago
|
Description
•