4 ms·

> It doesn't need a blocker for third-party scripting, service workers ... because the browser's technology simply doesn't recognise these page components I'd

> It doesn't need a blocker for third-party scripting, service workers ... because the browser's technology simply doesn't recognise these page components I'd never thought about it like that, but it's a nice side-effect. You don't have to worry about obtrusive JS, if your browser doesn't know what JS is. :D

zimpenfish 2y ago
> if your browser doesn't know what JS is It's worse than that[0] - Lynx statically renders the page at load time which means any "dynamic" updates just can't happen. I did have a bash at integrating the Mozilla JS engine but gave up after realising that anything more than just `document.write("flange")` handled at load time would need the entire inner engine rewriting and that was/is far beyond me[1]. [0] This is based off my memories of the Lynx source back in the Olden Times, ~1995-2000ish. [1] But I did do the original cookie jar and colour styles (as seen in the screenshots) work (`lynx.lss` is all my fault, sorry)