My worry is we would have to come up with a method to know what messages were needed to be stored and what were not. How many back. I would be worried that someone might have quite a refresh going on.
-----Original Message----- From: BRLTTY <[email protected]> On Behalf Of Aura Kelloniemi Sent: Wednesday, September 17, 2025 1:32 PM To: 'Informal discussion between users and developers of BRLTTY.' <[email protected]> Subject: Re: [BRLTTY] Is there a feature-compatible text-based browser Hi, On 2025-09-17 at 13:24 -0400, <[email protected]> wrote: > I would love to know if there are any documents on how people think a more > console based web browser should deal with dynamic web pages. The back end > can deal with it but We have to come up with a good way to deal with it with > the synths and displays we have. What are peoples ideas? The first idea that comes to my mind: show a message every time an element in the DOM tree changes. Store the locations of the changed elements in a list and provide a key binding for focusing the previous/next/first/last element in the update list. -- 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 _______________________________________________ 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
