Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
5.15.4
-
None
Description
Hello,
When
- running the attached script to monitor accessibility events,
- starting this
kdialog --textinputbox "foo"
- and typing the return key
The script prints:
got event object:text-changed:insert 0 1
adding
{{ 0x2029}}
now
{{ 0xa}}
i.e. the text-changed:insert event reports a U+2029 character insertion, while the character actually exposed through getText() is U+0A. The event should be fixed into reporting a U+0A character insertion, so that screen readers such as brltty which use both events and content do not get completly confused. Notably, gtk never reports U+2029, only U+0A.
Samuel