[Development] Fwd: Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Lisandro Damián Nicanor Pérez Meyer]

---------- Mensaje reenviado ----------
De: "Samuel Thibault" <sthibault at debian.org>
Fecha: 3 sep. 2017 3:34 p.m.
Asunto: Re: Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
huge negative performance impact, should not be always on
Para: "Allan Sandfeld Jensen" <kde at carewolf.com>
Cc: "Lisandro Damián Nicanor Pérez Meyer" <lisandro at debian.org>, "Sebastian
Humenda" <shumenda at gmx.de>, "Lisandro Damián Nicanor Pérez Meyer" <
perezmeyer at gmail.com>, "Alex ARNAUD" <alexarnaud at hypra.fr>, <
874054 at bugs.debian.org>, <debian-qt-kde at lists.debian.org>, <
development at qt-project.org>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170905/1262a921/attachment.html>