Closed
Bug 28904
Opened 26 years ago
Closed 26 years ago
keyboard shortcuts for Back and Forward are reversed
Categories
(SeaMonkey :: General, defect, P1)
SeaMonkey
General
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: cmaximus, Assigned: mcafee)
Details
(Whiteboard: [PDT+])
Overview Description:
The keyboard shortcuts for 'Back' and 'Forward' under the 'Go' menu are reversed. They are currently assigned as:
Back--> Ctrl-] and Forward--> Ctrl-[.
They should be the other way around.
All platforms 2000022108 builds and for sometime before that I'm sure.
I've assigned to law cuz someone told me he owned that menu.
In the future can fixes like this just go to you German?
Marking beta1 because:
* it looks like it's *really* easy to fix - i.e., change two letters of source
code.
* If the keys actually get working (see bug 29348), it would be *really*
annoying to have them backwards.
If it's more complicated than just changing two characters in navigator.dtd,
then maybe it doesn't need to be beta1, but...
Keywords: beta1
Yep, those are backwards all right. Lucky for us they seem to be broken ...
Assignee: law → mcafee
Severity: minor → normal
Priority: P3 → P1
Target Milestone: M14
![]() |
Assignee | |
Comment 4•26 years ago
|
||
fixed
![]() |
Assignee | |
Comment 5•26 years ago
|
||
fixed
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
![]() |
||
Comment 6•26 years ago
|
||
verif w/opt mozilla bits on linux, mac and winNT [200002290x].
Status: RESOLVED → VERIFIED
![]() |
||
Comment 8•25 years ago
|
||
Please don't use Ctrl-[/] for back/forward as you can't do this on
many 'foreign' (non-US) keyboards (like mine). What's the problem with Alt-left
and Alt-right? (at least on MS Windows it's the standard for Netscape,Opera,IE).
![]() |
Assignee | |
Comment 9•25 years ago
|
||
kurt: you should file a new bug, this one is fixed and
won't be looked at much. It will be much easier to
track & deal with your problem in a new bug.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•