Closed
Bug 1487121
Opened 6 years ago
Closed 6 years ago
proxyType is marked as optional but proxy.settings.set raises an error when it is missing
Categories
(WebExtensions :: Request Handling, defect)
WebExtensions
Request Handling
Tracking
(firefox63 verified, firefox64 verified)
VERIFIED
FIXED
mozilla63
People
(Reporter: rpl, Assigned: rpl)
Details
Attachments
(2 files)
proxyType is marked as optional in the API schema [1] and it is also documented on MDN as optional with "system" as its default value, but proxy.settings.set is currently raising an "undefined is not a valid value for proxyType." error when it is missing (https://searchfox.org/mozilla-central/rev/55da592d85c2baf8d8818010c41d9738c97013d2/toolkit/components/extensions/parent/ext-proxy.js#233). [1]: https://searchfox.org/mozilla-central/rev/55da592d85c2baf8d8818010c41d9738c97013d2/toolkit/components/extensions/schemas/proxy.json#28 [2]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/proxy/settings
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Comment on attachment 9004922 [details] Bug 1487121 - Allow proxy.settings.set calls without an explicit proxyType property. Shane Caraveo (:mixedpuppy) has approved the revision.
Attachment #9004922 -
Flags: review+
Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/f4ca43d3fc1b Allow proxy.settings.set calls without an explicit proxyType property. r=mixedpuppy
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f4ca43d3fc1b
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Updated•6 years ago
|
Assignee: nobody → lgreco
Comment 5•6 years ago
|
||
Is manual testing required on this bug? If yes, please provide some STR and the proper extension(if required) or set the “qe-verify -“ flag. Thanks!
Flags: needinfo?(lgreco)
I was able to reproduce this issue on Firefox 62.0(20180830143136) under Win 7 64-bit and Mac OS X 10.13.3. This issue is verified as fixed on Firefox 64.0a1(20180906232139) and Firefox 63.0b4(20180906162647) under Win 7 64-bit and Mac OS X 10.13.3. Please see the attached video.
Flags: needinfo?(lgreco)
You need to log in
before you can comment on or make changes to this bug.
Description
•