1589852 - Undo (ctrl-z) does not work in "File"/"Save As" dialog box

Status: UNCONFIRMED

(Core :: Widget: Gtk, enhancement)

Description

[L.I.A.R.]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

• Do anything to get a "File" (e.g. "Save As" or "Open File") dialog box to pop up.
  For instance, Right Click on background of any page and select "Save Page As"
• In the dialogbox that appears, the current filename/location will be highlighted/selected (if location does not appears, hit CTRL+L to switch to manually changing the location).
• Valuntarily/Erroneously hit a key (e.g. "a")
• Hit CTRL-Z

Actual results:

Nothing: CTRL-z (or any other "undo" key combination) is inactive in "File" dialog boxes.

Expected results:

CTRL-z (or any other "undo" key combination) should bring back the text that has been (voluntarily/erroneously) overwritten.

COMMENT: I don't use Gnome as my WM, but I think FF uses GTK, so it might be a GTK problem.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[L.I.A.R.]

Any news about a fix available someday?

The current behaviour is really blocking, particularly on laptop computers, where keys are so close to one another and the trackpad, that typing a key by mistake occurs more than often?

At least could you backup my bug report @gtk?
https://gitlab.gnome.org/GNOME/gtk/-/issues/1882

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Is that Firefox only problem or do you see that in other gtk based applications too? Like gedit.
Thanks.

Comment 4

[L.I.A.R.]

It's apparently a general Gnome problem (ah... those damn "interface nazis"...)

I've reported the bug here:
https://gitlab.gnome.org/GNOME/gtk/-/issues/1882

Comment 5

[L.I.A.R.]

Would be great if more people could back up the bug report, it does not seem to receive any attention....

Comment 6

[L.I.A.R.]

OK, so 3 years later, the bug has finally received some attention:
https://gitlab.gnome.org/GNOME/gtk/-/issues/2337

And the conclusion is that *this bug will not get corrected on Gtk3, but it is corrected in Gtk4.

So the question now is: When will FF move to Gtk4 (knowing the 4.8.1 is the latest stable release of Gtk... and Gtk 3.24 is considered and old stable release)?