Closed
Bug 51418
Opened 24 years ago
Closed 24 years ago
[meta] Accelerators we must have for all apps.
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
People
(Reporter: lake, Assigned: mcafee)
References
Details
(Keywords: meta, Whiteboard: [nsbeta3+])
These are the Accelerators that are Must Haves for all parts of Netscape6.
Additional Accelerators will be addressed in another bug. Accelerators that
differ in functionality depending on which app you are in have their own Must
Have and Additional buggs
Alt - Alt on Windows and Linux, Option on MacOS (unless stated otherwise)
Ctrl - Ctrl on Windows and Linux, Cmd on MacOS (unless stated otherwise)
Accelerator Behavior
Ctrl + A Select All
Ctrl + C Copy
Ctrl + G Find Again
Ctrl + M New Mail Message
Ctrl + P Print
Ctrl + Q Quit
Ctrl + V Paste
Ctrl + W Close
Ctrl + Y Redo
Ctrl + X Cut
Ctrl + Z Undo
Ctrl + 1 Navigator
Ctrl + 2 Messenger
Ctrl + 4 Composer
Ctrl + 6 Calendar
Ctrl + 7 Radio
Ctrl + 9 Instant Messenger
Ctrl+Shift+2 Address Book
Cmd . (Mac)
Esc (other) Stop
Del Delete
Codeing comentary is welcome here. Other comentary please see the tracking bug.
Comment 1•24 years ago
|
||
Chris: I can help out with this as needed.
Comment 2•24 years ago
|
||
--> keyboard navigation, setting se default qa
Component: Browser-General → Keyboard Navigation
QA Contact: doronr → sairuh
Reporter | ||
Comment 4•24 years ago
|
||
Yes this would.
Assignee | ||
Comment 7•24 years ago
|
||
adding timeless.
Assignee | ||
Comment 8•24 years ago
|
||
Adding dependency on bug 52217, accelerators with numbers show up in menus but
don't respond to that key sequence.
Depends on: 52217
Assignee | ||
Comment 9•24 years ago
|
||
I think I have all of these working (except the numeral-based
accelerators, see 52217) EXCEPT: Calendar & Radio, I don't
see these menu items anywhere.
Also, do we need an item for Net2Phone?
Assignee | ||
Comment 10•24 years ago
|
||
Also, what about IRC Chat?
Comment 11•24 years ago
|
||
IRC Chat, and AIM
ctrl+3 and ctrl+shift+1 were message center
ctrl+5 was conference
We could easily give them to AIM/IRC Chat. Personally I'd like 3 for Chat, and
aim can have shift+3 or 5.
Assignee | ||
Comment 12•24 years ago
|
||
Also, is there some sort of order for the numbered accelerators?
E.g it'd be nice if the Task menu's 1st item was "1", 2nd was "2", etc.
Assignee | ||
Comment 13•24 years ago
|
||
AIM was 9 in 4.x, so we have to decide between history & order.
Assuming history wins for now.
IRC, Net2Phone need items, and I'd like to get a better one for AddressBook.
How about:
1 Navigator
2 Mail
3 IRC (was Message Center)
4 Composer
5 Address Book (was Conference)
6
7 Net2Phone (was radio)
8
9 AIM
0
Note this would leave 6, 8, 0 free for other things.
Reporter | ||
Comment 14•24 years ago
|
||
OK I Am confused I am using the 4.x on the Mac and the PC They are different Mac
is:
Mac PC
Navigator 1 1
Mail 2 2
Composer 3 4
Calander 4 6
AIM 5 9
Radio 8 7
Adressbook Shift 8 Shift 2
News Groups Shift 3
So first we should have 1 for bothe they should be inorder on the menu and it
would be nice if we gave the high use high profile items the lower numbers.
Remember AIm is now a targeted high use item for 6.0 Here I think we should
break from duplicating the 4.x and just do it right for 6. This also preserves
the order for the taskbars main items.
So
Browser 1
Mail 2
AIM 3
Composer 4
Addressbook 5
Avaliable 6
Net2Phone 7
IRC 8
Avaliable 9
When a user has not loaded aome of the components like Mail that item would not
be in the menu so there may be some skipping but we already have that.
Comment 15•24 years ago
|
||
Hrm, IRC Chat is part of mozilla's distribution, AIM isn't.
In the interest of pairings, we could do:
1: Navigotor [C], Composer [CS]
2: Mail [C], Address Book [CS]
3: IRCChat and AIM - Mozilla.org's interests and Netscape.com's interest
diverge here. I'd prefer IRCChat to get C3 and AIM CS3, but the other way
around is fine.
4: Net2Phone [C], Conference [CS]
5: Radio [C]
6: Calendar [C]
C=Control [technically XULKey], S=Shift [I think shift is never xulkey and
always available?]
Does anyone from international object to this?
This leaves CS5, CS6 and 7-9,0
Assignee | ||
Comment 16•24 years ago
|
||
I don't like control-shift, and vote for trying the order
that lake suggests.
Comment 17•24 years ago
|
||
adding meta... lisa, should this be chopped up into smaller "quanta"? (see last
comments in bug 51600.) for example, could the need for accelerators for numbers
be a separate bug? the reason i'm concerned here is that the list of must-haves
here is rather broad --and the individual feature might get lost (as in the old
meta bug 22529, before the keyboard navigation component existed). thx!
Keywords: meta
Reporter | ||
Comment 18•24 years ago
|
||
The numbers should already be done in theory. I don't know when they will be
checked in, and I am prety sure that the Mcafee is the guy for these.
Let me know if I am wrong.
Assignee | ||
Comment 19•24 years ago
|
||
Fixed. Had to re-order some higher-numbered task items,
but they've got accelerators now. Please see bug 52217 about
numbers not working as accelerators on linux (maybe mac too).
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 20•24 years ago
|
||
okay, i'm doing a semi-rubberstamp verification (based on 2000.09.18.08/6 opt
comm bits). exceptions should/will be filed as seperate bugs.
for linux, winnt and mac, the following accelerated shortcuts are correct:
1 - navigator
2 - mail
3 - instant messenger
4 - composer
5 - address book
i've found that the accelerator for Net2Phone on winnt is ctrl+9, not ctrl+7 as
lake suggested above (methinks). let me know what the expected value for
Net2Phone should be (if what i see is wrong, i'll be happy to file a new bug,
prolly in bugscape since it's nsonly).
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Component: Keyboard: Navigation → User events and focus handling
Updated•6 years ago
|
Summary: Accelerators we must have for all apps. → [meta] Accelerators we must have for all apps.
You need to log in
before you can comment on or make changes to this bug.
Description
•