GNOME Bugzilla – Bug 112473
<escape> doesn't make find-dialog go away
Last modified: 2004-12-22 21:47:04 UTC
Don't know if that behaviour is intentionally/HIGish ... but I'd find it quite natural if the find-dialog would vanish on <escape>
I think this is notabug. Escape is usually bound to cancel which means get me out of here and undo anything i might have done. I think there may be an existing hig bug on the issue, and it appears that gtk automatically binds escape to Cancel in dialogs by default, hence i'd want this done at the gtk level, not at the epiphany level.
Dave I'm not sure if I get you. What should be done at gtk level ? What should be the behavior, forgetting who need to do it ?
the behavior is undecided, see hig bug 109194. I think unless there is a clear decision in that bug that escape should close dialogs (and i think there are some strong conceptual reasons not to do this), that we should not do this and mark this notabug.
I see, I agree
So it's NOTABUG for now. If there a decision on that bug, we will change it.
*** Bug 116270 has been marked as a duplicate of this bug. ***
*** Bug 126144 has been marked as a duplicate of this bug. ***
*** Bug 129082 has been marked as a duplicate of this bug. ***
I do not know a but or notabug it is. But current behaviour is not convenient (at least 4 people already complained about it). In general bug is a behaviour of program that confuses or annoys the program's user. The second vote for "a bug" is that there are many dialogs that can be closed by ESC. At least it's inconsistent...
The current behavior will stand until there is a HIG decision on the correct behavior. At least two HIG maints have clearly stated that escape != close and that all bugs related to this have arose only from find dialogs.
*** Bug 133899 has been marked as a duplicate of this bug. ***
*** Bug 143981 has been marked as a duplicate of this bug. ***
*** Bug 148396 has been marked as a duplicate of this bug. ***
*** Bug 151510 has been marked as a duplicate of this bug. ***
*** Bug 153980 has been marked as a duplicate of this bug. ***