Consider removing `privacy.network.tlsVersionRestriction`
Categories
(WebExtensions :: General, task, P3)
Tracking
(Not tracked)
People
(Reporter: willdurand, Unassigned)
References
Details
(Whiteboard: [addons-jira])
We think we can safely remove this API.
|
||
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
It looks like we never used this api in secure-proxy, and it is otherwise unused. Can you verify :baku?
|
||
Comment 3•2 years ago
|
||
This API was introduced in bug 1593635, and has never offered any useful functionality besides privileged extensions.
Calling browser.privacy.network.tlsVersionRestriction.get() results in a rejection with "Error: tlsVersionRestriction can be set by privileged extensions only."
Although the message suggests that the privileged-only restriction is supposedly only for setters, in practice it also applies to the getter. I verified that this restriction is present in all versions from Firefox 72 (where the API was added, by bug 1593635), until the latest (129).
Moreover, the documentation that was added in bug 1593635 ended up in the wrong place. The API is NOT documented at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy/network but at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/browserSettings/tlsVersionRestrictionConfig . Note that it is not only in the wrong location, but also documented as a non-existing browserSettings.tlsVersionRestrictionConfig property.
Since we haven't seen any usage, and the API is effectively undocumented, we should just remove the unused code and delete the wrong documentation.
Description
•