The component should use the WASIX networking layer to fetch HTTP responses through virtual-net (see #412), and then display the responses as actual HTML.
To be framework agnostic, this could be implemented as a web component.
One main challenge here is that this needs to use an actual HTTP client to do requests and parse responses.
We will probably want to write the whole component in Rust so it can use hyper as the http client.
Alternatively we could just implement the client itself in Rust, and have a fetch export that allows doing http requests in the internal network from JS.
There is a wide set of features we could implement here.
How much of this should be included in the initial implementation must be discussed.
Potential features:
[ ] Integrate with browser history by persisting the nested URL in the main url (subpath, as a query param, ...)
linear[bot]
commented
10 months ago
Implement a reusable
WebBrowsercomponent.The component should use the WASIX networking layer to fetch HTTP responses through virtual-net (see #412), and then display the responses as actual HTML.
To be framework agnostic, this could be implemented as a web component.
One main challenge here is that this needs to use an actual HTTP client to do requests and parse responses. We will probably want to write the whole component in Rust so it can use hyper as the http client. Alternatively we could just implement the client itself in Rust, and have a
fetchexport that allows doing http requests in the internal network from JS.There is a wide set of features we could implement here. How much of this should be included in the initial implementation must be discussed.
Potential features: