META bug for Mailnews Front End accessibility

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Sean Su, Unassigned)

Tracking

(Depends on: 6 bugs, {access, meta})

Trunk
access, meta
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
This is the meta bug for all front end accessibility issues within mailnews
(Reporter)

Updated

16 years ago
Status: NEW → ASSIGNED
Depends on: 154247, 154248
Keywords: access
(Reporter)

Updated

16 years ago
Depends on: 154252

Comment 1

16 years ago
Just informative note: there is also Browser meta bug 129179 with mnemonics
issues for Browser and Mail.

Updated

16 years ago
Keywords: meta
(Reporter)

Updated

16 years ago
Depends on: 158199

Comment 2

16 years ago
Added keyword nsbeta1 to 8 UI Mailnews meta bugs.
Keywords: nsbeta1

Updated

15 years ago
Keywords: nsbeta1

Updated

15 years ago
Depends on: 165999

Updated

14 years ago
Depends on: 224728

Comment 3

14 years ago
added one more related bug to dependency list
Depends on: 119192
Product: Browser → Seamonkey

Updated

10 years ago
No longer depends on: 21342
Assignee: ssu0262 → mail
Status: ASSIGNED → NEW
QA Contact: olgam

Comment 4

9 years ago
MASS-CHANGE:
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

Comment 5

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.