Hi list, On 2025-09-17 at 10:55 -0400, <[email protected]> wrote: > Then let me back track. I have not used lynx since 2001. That is when I > Switched from Linux as my default machine. Things sound like they are > different so I will check and see if the interface is as bad as I remember > before I give up on it.
> I still am not sure I want to be locked into lynx as an interface. The user interface is a matter of configuration (and of course, implementing the configuration options). But it is entirely a different question to design a browser in a way that it either supports dynamic rendering of contents or does not. Turning Lynx into a browser which has a notion of dynamically changing DOM is probably going to be very difficult as the browser has not been designed to support this. Building a new browser interface which emulates Lynx is not that bad at all, if the user interface is designed to be customizable. And don't even know if there is any point in implementing a static web browser with JavaScript support. I once did this. I bolted elinks to preprocess web pages using PhantomJS (this was trivial). It worked, kind of, but most sites looked almost the same as without any JavaScript execution as the contents were not dynamically updated. Some sites which worked without JavaScript stopped working altogether, because PhantomJS disregarded <noscript /> elements. There was basically no gain and I never used this browser in practice. -- AUra _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
