Closed Bug 68243 Opened 24 years ago Closed 13 years ago

add mnemonics to all prefs panels

Categories

(SeaMonkey :: Preferences, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jruderman, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access, Whiteboard: [Halloween2011Bug])

german said in bug 18575 that he was working on a spec listing the accesskeys for the various prefs panels. (Btw, should the "Category" pane get an accesskey that is active no matter which pane is selected?) Making the accesskeys actually *work* after they're added depends on bug 959 and maybe bug 64150.
Depends on: 40759
Blocks: 18575
methinks this should live in either the prefs or keybd nav component [easier to search for me]. i'll keep it assigned to german, tho', since he's writing up the spec for it. if anyone really wants this back in ui/df, pls do keep me on the cc list. thx! dependency confusion: wouldn't 40759 actually be dependent on this one?
Component: User Interface: Design Feedback → Preferences
Depends on: Accesskey-XUL
Keywords: access
QA Contact: mpt → sairuh
> should the "Category" pane get an accesskey that is active no matter which pane > is selected? No, it should be accessed using Control+Tab. > wouldn't 40759 actually be dependent on this one? Nope. Bug 40759 must be fixed before this bug can properly be marked fixed.
Over to Marlon.
Assignee: german → marlon
i think this belongs in aaron's domain. not sure what spec german was working on. aaron?
Once 959 is marked fixed, I'm going to farm these out - there are a lot of them.
I'll take it.
Assignee: marlon → aaronl
Blocks: accesskey
hi,this is a test!
hi,this is a test!
Blocks: patchmaker
Keywords: helpwanted
Product: Browser → Seamonkey
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Is this bug still valid for the current trunk? Unless I misunderstood this bug, for the following build: Build identifier: Mozilla/5.0 (Windows NT 6.0; rv:2.0b12pre) Gecko/20110218 Firefox/4.0b12pre SeaMonkey/2.1b3pre, this is WORKSFORME.
Mozilla/5.0 (X11; Linux x86_64; rv:10.0a1) Gecko/20111017 Firefox/10.0a1 SeaMonkey/2.7a1 ID:20111017003001 The prefs dialog has been completely rewritten as part of the Toolkit Transition for SeaMonkey 2. All panes & widgets are now in taborder, accesskeys exist on the right pane, so that part is WFM. Categories still have no accesskeys but they can be selected by ← ↓ ↑ → so I suppose adding accesskeys to specific categories is WONTFIX. IanN?
Whiteboard: [Halloween2011Bug][CLOSEME WFM/WONT?]
WONTFIX for the remaining part as per IanN over IRC.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
We won't fix categories with the current tree design.
Keywords: helpwanted
Whiteboard: [Halloween2011Bug][CLOSEME WFM/WONT?] → [Halloween2011Bug]
You need to log in before you can comment on or make changes to this bug.