After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794408 - Unicode combining diacriticals makes insertion/deletion in subsequent text be off by one
Unicode combining diacriticals makes insertion/deletion in subsequent text be...
Status: RESOLVED NOTGNOME
Product: evolution
Classification: Applications
Component: Composer
3.26.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2018-03-16 17:54 UTC by Stephen
Modified: 2018-03-22 15:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephen 2018-03-16 17:54:18 UTC
Editing text following a combining diacritical (and probably other combining characters) causes off-by-one style insertion/deletion errors in subsequent text.


To reproduce:

* Begin composing an message with either plain text or HTML formatting

* Paste the following (the 'á' below is an 'a' followed by b'\xcc\x81'):

á some text here

* Insert or delete text anywhere before the end of the following text.


In contrast, the same but with a single char representing 'á' doesn't have the same buggy behaviour:

á some text here
Comment 1 André Klapper 2018-03-16 18:46:34 UTC
Assuming that's U+0301: Confirming.
Comment 2 Milan Crha 2018-03-22 14:29:57 UTC
Thanks for a bug report. I can reproduce it too, but in WebKitGTK+'s MiniBrowser, thus the problem is there. I filled [1] in their bugzilla. I'm closing this, because there's nothing we can do about it on the Evolution side.

[1] https://bugs.webkit.org/show_bug.cgi?id=183898
Comment 3 Milan Crha 2018-03-22 14:49:36 UTC
I just realized that WebKitGTK+ 2.20.0 has this fixed.
Comment 4 Stephen 2018-03-22 15:02:31 UTC
Yep, and actually webkitgtk4 (as not-at-all confusingly-named in Fedora 27!) is at 2.20.0 in F27 updates-testing, and fixes this bug in Evo/MiniBrowser :)