Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.

Isn't it more like a TTY mode of VNC more apt? E.g., rendering the X commands as ASCII?

Ah, noted.

Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!

Browsh does some js, and felinks is an actively maintained fork of elinks with some js support as well.

Elinks is the only one close, but last I tried it there were still issues

Terrible suggestion.

From [1]

"On 17 March 2017, OpenBSD removed ELinks from its ports tree, citing concerns with security issues and lack of responsiveness from the developers.[5]"

Last stable is from 2009. Last development release 2012. Elinks is dead. Realize it uses an old version of Spidermonkey (JS). Elinks should not be used in a production environment, period.

[1] https://en.wikipedia.org/wiki/Elinks

links, on the other hand, is current. (Works on Windows, too.)

I don't think there's a single reason to use a text-based browser in a production environment.

browsing through SSH

Not just browsing (the web) - the idea of an HTML-based application UI can be extended to the text mode instead of getting stuck with the choice between a GUI and a command-line (or a custom curses-based) interface. (Imagine VSCode running in a terminal!)

I think you're perfectly able to understand what I meant there: anything other than research purpose in an isolated environment e.g. sandbox.

edbrowse has minimal js support thru duktape.

w3m hasn't, thank goodness.

some find that as a perk.

I like Links more than Lynx.