News for hackers. Stuff that matters.
Re:Lightpanda migrate DOM implementation to Zig by parhamn on Monday January 12, 2026 @06:05AM (#46586819)
Off topic note: I read the website and a few pages of the docs and it's unclear to me for what I can use LightPanda safely. Like say I wanted to swap my it as my engine on playwright, what are the tradeoffs? What things are implemented, what isnt?
Re:Lightpanda migrate DOM implementation to Zig by fbouvier on Monday January 12, 2026 @06:40AM (#46587100)
Thanks for the feedback, we will try to make this clearer on the website. Lightpanda works with Playwright, and we have some docs[1] and examples[2] available.

Web APIs and CDP specifications are huge, so this is still a work in progess. Many websites and scripts already work, while others do not, it really depends on the case. For example, on the CDP side, we are currently working on adding an Accessibility tree implentation.

[1] https://lightpanda.io/docs/quickstart/build-your-first-extra...

[2] https://github.com/lightpanda-io/demo/tree/main/playwright

Re:Lightpanda migrate DOM implementation to Zig by epolanski on Monday January 12, 2026 @07:58AM (#46587807)
I was actually interested into using lightpanda for E2Es to be honest, because halving the feedback cycle would be very valuable to me.
Re:Lightpanda migrate DOM implementation to Zig by infogulch on Monday January 12, 2026 @12:51PM (#46591828)
Maybe you should recommend a recipe for configuring playwright with both chromium and lightpanda backends so a given project can compare and evaluate whether lightpanda could work given their existing test cases.
Re:Lightpanda migrate DOM implementation to Zig by h33t-l4x0r on Monday January 12, 2026 @06:35AM (#46587059)
I think it's really more of an alternative to JSDom than it is an alternative to Chromium. It's not going to fool any websites that care about bots into thinking it's a real browser in other words.