zlacker

[return to "Show HN: One Human + One Agent = One Browser From Scratch in 20K LOC"]
1. hedgeh+KV1[view] [source] 2026-01-27 21:18:34
>>embedd+(OP)
This looks pretty solid. I think you can make this process more efficient by decomposing the problem into layers that are more easily testable, e.g. testing topological relationships of DOM elements after parse, then spatial after layout, then eventually pixels on things like ACID2 or whatever the modern equivalent is. The models can often come up with tests more accurately than they get the code right the first time. There are often also invariants that can be used to identify bugs without ground truth, e.g rendering the page with slightly different widths you can make some assertions about how far elements will move.
◧◩
2. socalg+Gc3[view] [source] 2026-01-28 06:41:11
>>hedgeh+KV1
the modern equivalent is the Web Platform Tests

https://web-platform-tests.org/

◧◩◪
3. hedgeh+d15[view] [source] 2026-01-28 17:44:44
>>socalg+Gc3
Amazing. I think if I were taking on the build-a-browser project I would pair that with the WhatWG HTML spec to come up with a task list (based on the spec line-by-line) linked to specific tests associated with each task. Then of course need an overall architecture and behavioral spec for how the browser part behaves beyond just rendering. A developer steering process full time might be able to get within 80% parity of existing browsers in a month. It would be an interesting experiment.
[go to top]