You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Members of this Working Group have agreed not to progress the TCP UDP Sockets API specification further as a Recommendation track document, electing instead to publish it as an informative Working Group Note under a permissive license with a view to enabling it to form the basis of further work by others, e.g. in a W3C Community Group.
I think ideal steps would be:
1. Create a new bug something like "WebExtensions API for client TCP sockets" (i.e., no UDP no server sockets)
2. Make a proposal for how an extension uses this API and when and how users of such extensions are notified and grant permission (i.e., do they get a prompt when an extension is installed? Every time a socket is connected? Just the first time an extension connects to a specific address/port?)
Once we have consensus on that, the implementation won't be completely trivial but it should be pretty straightforward.
The text was updated successfully, but these errors were encountered: