Closed
Bug 187059
Opened 23 years ago
Closed 22 years ago
Shift+Ctrl+G (Find Previous) doesn't work
Categories
(Firefox :: General, defect, P3)
Tracking
()
RESOLVED
FIXED
Firebird0.8
People
(Reporter: jruderman, Assigned: mconnor)
References
Details
Attachments
(1 file)
2.99 KB,
patch
|
p_ch
:
review+
|
Details | Diff | Splinter Review |
Ctrl+Shift+G for Find Previous doesn't work in Phoenix. This is a problem with
both Edit>Find and typeahead find. cf bug 171747 for F3.
Reporter | ||
Comment 1•23 years ago
|
||
I'm using a 12/27 build on Windows XP.
![]() |
||
Comment 2•23 years ago
|
||
Didn't know it was supposed to do that.
http://texturizer.net/phoenix/keyboard.html
Related to bug 184050?
![]() |
||
Updated•23 years ago
|
OS: Windows XP → All
Summary: ctrl+shift+g doesn't work (find previous) → Shift+Ctrl+G (Find Previous) doesn't work
![]() |
||
Comment 4•22 years ago
|
||
What programs use this shortcut?
Other than Mozilla? I have no idea. I'm fine toasting Ctrl[Shift+]G completely
and only supporting [Shift+]F3.
*** Bug 208597 has been marked as a duplicate of this bug. ***
As the "author" of a <A
HREF=http://bugzilla.mozilla.org/show_bug.cgi?id=208597#c5>related report</A>
for the same bug, I'm glad to see that A) they're not dropping Ctrl-Shift-G, and
B) there's a solution ready to go into the next release.
![]() |
Assignee | |
Comment 8•22 years ago
|
||
due to bug 186789, any Ctrl+Shift shortcuts won't work on GTK2 platforms, I
suggest that while we could implement this for backwards compatibility, no UI or
help files should reference this as it is not a cross-platform solution
Updated•22 years ago
|
QA Contact: asa
![]() |
Assignee | |
Comment 9•22 years ago
|
||
we support Ctrl+G, so we should support Ctrl+Shift+G
this won't work on GTK2 builds, per the bug I mentioned.
this also moves certain values from farther down the list in browser.dtd to
where they should be (with the rest of the find access/command keys)
![]() |
Assignee | |
Comment 11•22 years ago
|
||
Comment on attachment 132170 [details] [diff] [review]
add Ctrl+Shift+G support back in
more for the pile
Attachment #132170 -
Flags: review?(noririty)
![]() |
Assignee | |
Updated•22 years ago
|
Status: NEW → ASSIGNED
Comment 12•22 years ago
|
||
aside: I've always wondered why we allow the key to be modified in the .dtd but
hard-code the modifiers.
![]() |
Assignee | |
Updated•22 years ago
|
Severity: normal → minor
Priority: -- → P3
Target Milestone: --- → Firebird0.8
Comment 13•22 years ago
|
||
further aside: Maybe we should try and start the trend of putting the modifiers
into the .dtd as well. Then you'd have |modifiers="&findPrevCmd.modifiers;|,
with a corresponding entry in the .dtd. This would be much easier to localize,
in case there's a different standard for a shortcut key in another locale. Any
thoughts?
![]() |
Assignee | |
Updated•22 years ago
|
Attachment #132170 -
Flags: review?(noririty) → review?(p_ch)
![]() |
Assignee | |
Comment 14•22 years ago
|
||
maybe look at it in another bug, I'm not sure whether other locales do in fact
use different accesskeys (although if we did, that would probably cause more
headaches than anything if a localizer broke common shortcuts by using this)
![]() |
||
Comment 15•22 years ago
|
||
Ctrl-shift-G is the correct shortcut for linux: from the Gnome HIG (chapter 10,
keyboard navigation):
Use Shift-Ctrl-letter for functions that reverse or extend another function. For
example, Ctrl-Z and Shift-Ctrl-Z for Undo and Redo. Note that you cannot use
Shift-Ctrl-A-thru-F, however, as these combinations are used to enter unicode
characters in text fields.
![]() |
||
Comment 16•22 years ago
|
||
Comment on attachment 132170 [details] [diff] [review]
add Ctrl+Shift+G support back in
r=me, but there was no need to add <!ENTITY findPrevCmd.commandkey "g">, you
could have reused findAgainCmd.commandkey
Attachment #132170 -
Flags: review?(p_ch) → review+
![]() |
||
Comment 17•22 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•