Open Bug 1467145 Opened 2 years ago Updated 2 months ago
https://searchfox.org/mozilla-central/source/dom/network/TCPSocket.h#40 - there's a bunch of code, including some IPC handlers, which appears to exist only to support this. From some simple grepping, it appears to be unused. :froydnj suggested that it may be the case that we're interested in exposing this to webExtensions in the future, CCing :aswan for feedback on that.
We have had bug 1247628 for some time but never made much progress, mostly because there are many things a malicious extension could do with direct access to TCP sockets and we haven't figured out how to present to users a concise description of what such an extension can do that lets them make an informed decision about whether to install the extension or not. I think you should feel free to remove this, if we come to a point where we want to expose sockets to extensions, we can pull this code out of the repository and make it work again, but there's no point continuing to maintain and ship it just in case. CCing a couple of other folks who may (or may not) want to weigh in.
See Also: → libdweb-udp
Bug 1247628 is in the backlog for WebExtensions, but it is not on the radar for implementation right now. I do believe we will get to it (in some form) eventually, particularly as interest in distributed web protocols keeps growing. I don't know when that will be, but I feel pretty confident saying that Mozilla is unlikely to do anything in 2018.
I think we're probably going to want this relatively soon, so removing the implementation and letting it bit rot does not seem like a great idea.
Moving to the dom component as the discussed code lies there...
Component: Networking → DOM
Component: DOM → DOM: Core & HTML
Severity: normal → --
Component: DOM: Core & HTML → DOM: Networking
Priority: P3 → --
Severity: -- → N/A
Type: enhancement → task
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.