browser.downloads.download does not accept data: urls
Categories
(WebExtensions :: Untriaged, defect)
Tracking
(firefox133 affected, firefox134 affected, firefox135 affected)
People
(Reporter: tblodt, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:133.0) Gecko/20100101 Firefox/133.0
Steps to reproduce:
In an extension with downloads permission: chrome.downloads.download({url: 'data:,'})
Actual results:
Uncaught Error: Type error for parameter options (Error processing url: TypeError: URL constructor: is not a valid URL.) for downloads.download.
Expected results:
Create a download whose contents are from the data url.
|
||
Comment 1•7 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•5 days ago
|
||
Hello,
I’m not sure I reproduced the issue as what I see in the console is slightly different from what was mentioned in Comment 0. Tested on the latest Nightly (135.0a1/20241126205118), Beta (134.0b1/20241125200000) and Release (133.0/20241121140525) under Windows 10 x64 and Ubuntu 24.04 LTS.
I installed https://addons.mozilla.org/en-US/firefox/addon/s3download-statusbar/ which has the downloads permission and then I ran chrome.downloads.download({url: 'data:,'}) in the add-on console.
The result I obtained is as follows: Uncaught Error: Type error for parameter options (Error processing url: Error: Access denied for URL data:,) for downloads.download.
In case the STR I used are not correct, do provide some more details. Thank you !
I must have pasted the wrong thing or something - I just tried again and got the same error string as you. Uncaught Error: Type error for parameter options (Error processing url: Error: Access denied for URL data:,) for downloads.download. This is what I remember the error being (Access denied).
|
|
||
Comment 4•4 days ago
|
||
Hi tbodt ! Thank you for confirming !
I will mark the versions I tested yesterday as affected and set the bug report to New.
Description
•