On 17/11/2021 22:02, dan d. wrote:
For that matter, is there a general solution for web pages which refuse lynx
for that reason?
There can't be any general solution other than to use a browser that fully
implements HTML 5, EcmaScript, and the associated browser and document and CSS
object models. That would be such a radical rewrite that would have little or
no original code, or code structure, left.
I believe other text browser implement certain common idioms, but are not
general solutions.
I'm not convinced it is possible in a text browser, but the way to do it would
be to put a character cell rendering engine onto the Firefox or Chrome
engines, not to adapt the Lynx code.
(To get something that worked well in text-only, but only for well written
pages, you would also need to fully implement Aria support. This is a way of
telling accessibility tools the real semantics of the page, even when the HTML
semantics are only used for visual effect, and therefore requires
accessibility aware authoring.)