GNOME Bugzilla – Bug 794723
Selecting text and unselecting it in the mail editor makes it randomly disappear/deleted
Last modified: 2019-02-01 06:48:54 UTC
See summary. When selecting text in the mail editor, especially quoted text from the mail replied to, it is simply deleted from the mail. This is with evolution 2.28.0 and webkit 2.20.0.
The deletion happens when unselecting the text again, and on IRC it was reported that the same also happens in epiphany. So probably a webkit bug.
I can't reproduce this behavior in Epiphany. :(
Created attachment 370195 [details] screencast using epiphany tech preview
Still can't reproduce :/ but yes, it's surely a WebKit bug. I don't know how we're going to debug this, though.
I've just updated to the latest version of Epiphany Tech Preview, and we're both testing on this same Bugzilla page, so it's surprising that we're getting different results....
Created attachment 370198 [details] second screencast with epiphany tech preview
Thanks for a bug report. I'd probably move this to epiphany, if it can be reproduced there as well, because I'm most likely not able to do anything with it from the Evolution side. One thing about Evolution, it creates an autosave in a one minute interval after "the last" change. When this happens, then the selected text is unselected (not deleted). That's probably a different thing, right? I watched both of the videos and even I see the result of the actions in the text area, I do not see what those actions were. Could you write detailed steps, please? In case you've been just selecting various portions of the text, could it be that you began the drag above selected area, thus, instead of starting a selection, you moved the previously selected text elsewhere? hough I'm not able to reproduce the text disappear even with intentional drag&drop of the text portion.
I can reproduce with epiphany 3.27.90-58-gf0e577e with WebKitGtk+ 2.20.0 from gnome-nightly's flatpak. And, also evolution 3.28.0-4 and epiphany-browser 3.28.0.1-1 with WebKitGtk+ 2.20.0-dmo2 from current Debian Testing, at the same time.
BTW, running under gnome-shell as Wayland compositor.
Thanks for taking the time to report this. This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
(In reply to Michael Catanzaro from comment #10) > Thanks for taking the time to report this. > This issue is most likely a bug in WebKit. Please report the bug to > https://bugs.webkit.org/ including a link to this bug report and noting the As you could see in the "See also" field, it was already reported at: https://bugs.webkit.org/show_bug.cgi?id=184446
It seems this is a GTK+ bug: https://gitlab.gnome.org/GNOME/gtk/issues/132 However, since it is already reported in GitLab, not in Bugzilla, we cannot close as DUPLICATED instead of NOTGNOME, which would be the proper resolution.
(In reply to Andres Gomez from comment #12) > It seems this is a GTK+ bug: > https://gitlab.gnome.org/GNOME/gtk/issues/132 > > However, since it is already reported in GitLab, not in Bugzilla, we cannot > close as DUPLICATED instead of NOTGNOME, which would be the proper > resolution. Are you sure? I doubt WebKitGTK+ uses GtkTextView in the background. And the issue you referenced also mentions scrolling, not selected text deletion.
It was an input methods bug, and it's already fixed, see https://bugs.webkit.org/show_bug.cgi?id=184446
Ah, I see, the common part of the both. According to the webkit bug, it broke with commit e8bffe0c56431710299cf68afb575ec578045055 and had been fixed with commit 4b95d7406821196615149fb2527840ff14626a03, both in gtk+, thus I'm correcting the bug resolution from NotGnome, but Fixed.
*** Bug 795767 has been marked as a duplicate of this bug. ***
*** Bug 795721 has been marked as a duplicate of this bug. ***
*** Bug 796417 has been marked as a duplicate of this bug. ***
This is not fixed, see: https://gitlab.gnome.org/GNOME/gtk/issues/1447