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 785787 - headerbar and other gtk text entry items lacks undo/redo feature
headerbar and other gtk text entry items lacks undo/redo feature
Status: RESOLVED DUPLICATE of bug 322194
Product: gtk+
Classification: Platform
Component: Widget: Other
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-08-03 18:13 UTC by Asif Ali Rizvan
Modified: 2017-08-04 00:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gedit, undo not possible for lineedit in pop overs and headerbars (20.18 KB, image/png)
2017-08-03 18:13 UTC, Asif Ali Rizvan 		Details

Description Asif Ali Rizvan 2017-08-03 18:13:12 UTC 
Created attachment 356885 [details]
gedit, undo not possible for lineedit in pop overs and headerbars

Maps, Nautilus, and other apps where we can type URL or some text has no Undo/Redo functionality.

How to reproduce:
1. open maps, type some name
2. press ctrl+z to undo, undo won't happen.

1. open nautilus
2. press ctrl+l and type something
3. press ctrl+z to undo the text entered
4. won't happen

1. in gedit, the pop over text entry / line-edit also can't undo typed text
Comment 1 Daniel Boles 2017-08-04 00:05:45 UTC 
Currently GTK+ does not implement undo/redo for Entry; that is left to the responsibility of the application. See the documentation for GtkEntryBuffer:

"GtkEntryBuffer may be derived from. Such a derived class might allow text to be stored in an alternate location, such as non-pageable memory, useful in the case of important passwords. Or a derived class could integrate with an application’s concept of undo/redo."

In terms of possibly having this in GTK+, I think that is a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=322194

*** This bug has been marked as a duplicate of bug 322194 ***