FawkesWeb

What it does

Under the WPF shell is a complete, if small, stack: an HTML parser with its own DOM, a CSS engine with a cascade, a layout and rendering pass, and JavaScript execution with an event loop and a bridge into the DOM. No embedded WebView, no Chromium, no hundreds of megabytes of runtime.

Now the part that belongs before the purchase rather than after it: this is an experiment. It was written to see how far a hand-built browser stack gets. It does not replace a real browser. Pages built for modern engines will render imperfectly or not at all — that is the state of it, not a teething problem.

What it is good for: viewing simple and local HTML documents, watching a cascade and a layout resolve a page, and seeing what a browser actually does when nothing does the work for it. The seven-day trial is here precisely so you can try it against your own pages before deciding.

The window with its address bar and the buttons for cookies, the TOR network and AI summaries. The start page shows the three built-in panels — RSS reader, calendar preview and IMAP inbox — filled with placeholders here.

What you get out of it

• Its own engine instead of an embedded Chromium — the whole path from HTML to pixels.
• HTML parser, DOM, CSS cascade, layout, rendering and JavaScript in one program.
• Small, with no bundled browser runtime.
• Runs on Windows on .NET Framework 4.7.2.
• Shows how a page is resolved instead of hiding it behind a finished engine.
• A seven-day trial to find out on real pages what works and what does not.

What people use it for

Requirements

• PlatformWindows
• Runtime.NET Framework 4.7.2 · WPF
• CategoryInformations