Thanks for the suggestion. This is the first request for an HTMLViewer-style control in Web projects, so it's helpful to hear more about the use case before we think about the design space.
For context on why it doesn't exist today: Web projects deliberately don't accept arbitrary HTML, CSS, or JavaScript. The browser runs a fixed first-party client built around the control set, and your application code stays on the server - content only crosses that boundary through the typed browser protocol. That's a load-bearing part of the V1 security model, so anything like an HTMLViewer would be the first intentional exception to it, and I'd want to design the sandboxing, content-security, and navigation behaviour properly rather than bolt it on.
To help me understand what you need:
- Is the content something your app itself generates (formatted reports, documentation, rich text), or external web pages you want to embed by URL?
- Does it need to interact with the rest of the app —(e.g. respond to app state, raise events) or is it display-only?
- Roughly what do the pages/documents look like in practice?
If the common case turns out to be "display nicely formatted text my app produces", something like a sanitised Markdown viewer might serve that better and more safely than a general-purpose HTML embed. If it's genuinely "show this third-party page inside mine", that's a different conversation (and a harder one - many major sites refuse to be framed at all). Knowing which it is would help me scope this.