Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:31:58 +0200, wrote: > Note, the case where I saw the largest performance impact was not moving > the cursor, it was self-modifying web-content, it would send every text > change > in the active focus. [...] > But it is what Chrome would send on macOS and Windows when a > screen-reader is detected as active.
Uh. While it can be necessary to get such information. Getting every text change is the kind of spurious event I'm referring to. It should throttle the sends, to avoid the flurry that the screen reader won't be able to render as speech or braille anyway, and just make sure that the last version is sent. Samuel
