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
Currently, the Browser's Client API requires a global WebSocket API available, which is only the case for the WebView/headles platform as of now.
In order to make the Browser available on the node.js side, the POLYFILLS.mjs should also include a WebSocket polyfill that implements the client-side WS13 protocol.
Backport the crux.socket.WS implementation from lycheejs.
Backport the WebSocket() API usage to have a 1:1 replacement.
Implement a review for the base.mjs file.
The text was updated successfully, but these errors were encountered:
cookiengineer
changed the title
Browser: Client needs a WebSocket Polyfill
Base: WebSocket Polyfill
Apr 9, 2020
Stealth is now so modular that both the Browser and Tab interface are compatible with the browser Project and also can run in the node.js context.
Therefore the browser, as of now, only consists of Browser.mjs and ENVIRONMENT.mjs that both have DOM and Web API dependencies. Everything else is completely isomorphic, so that Stealth can run as a headless Browser now, too.
Currently, the Browser's Client API requires a global
WebSocket
API available, which is only the case for the WebView/headles platform as of now.In order to make the Browser available on the node.js side, the POLYFILLS.mjs should also include a
WebSocket
polyfill that implements the client-side WS13 protocol.WebSocket()
API usage to have a 1:1 replacement.base.mjs
file.The text was updated successfully, but these errors were encountered: