←back to thread

233 points monax | 1 comments | | HN request time: 0.341s | source

We’ve been working on Vaev, a minimal web browser engine built from scratch. It supports HTML/XHTML, the CSS cascade, @page rules for pagination, and print-to-PDF rendering. It even handles calc(), var(), and percentage units—and yes, it renders Google.com (mostly).

This is an experimental project focused on learning and exploration. Networking is basic (http:// and file:// only), and grid layouts aren’t supported yet, but we’re making progress fast.

We’d love your thoughts and feedback.

Show context
khimaros ◴[] No.44024102[source]
i find myself requesting this whenever i see a new minimalist browser pop up:

it would be great to standardize alternative browsers on a consistent subset of web standards and document them so that "smolweb" enthusiasts can target that when building their websites and alternative browsers makers can target something useful without boiling the ocean

i personally prefer this approach to brand new protocols like Gemini, because it retains backward compatibility with popular browsers while offering an off ramp.

replies(7): >>44024337 #>>44024442 #>>44024575 #>>44024868 #>>44027725 #>>44036733 #>>44041548 #
userbinator ◴[] No.44024442[source]
The subset could just be an older version of the spec, e.g. HTML 4.01 and CSS 2.1.

(My opinion as another one who has been slowly working on my own browser engine.)

replies(9): >>44024611 #>>44024625 #>>44024768 #>>44024884 #>>44025202 #>>44026019 #>>44027027 #>>44028487 #>>44028547 #
1. GoblinSlayer ◴[] No.44028547[source]
Sites often get that wrong. I'd say support motherfuckingwebsite.com subset: <p>, <a>, <h*>, <img>, <ruby> (i.e. markdown/gemini++) and do everything else with webcompat/fixbrowser way.