bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Accesskey of "Edit Link in New Composer" should be "E" not "i"

RESOLVED EXPIRED

Status

SeaMonkey
Composer
--
minor
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Matti, Unassigned)

Tracking

({access, polish})

Trunk
x86
Windows XP
access, polish

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316

As E is the hotkey to edit a page from the browser, so should it be from the editor.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

14 years ago
According to
XUL Accesskey FAQ and Policies
How do I pick an accesskey letter?
3. Make it easy to see
    * Avoid Letters (...) that are only one pixel wide, such as i or l.
http://www.mozilla.org/projects/ui/accessibility/accesskey.html

Steps to reproduce:
1. Create a simple link in a Composer page
2. Right-click on the link
3. Context-menu offers "Edit Link in New Composer"

Actual results: the first "i" is the accesskey

Expected results: "E" can/should be the accesskey

CONFIRMING

Mozilla 1.8a3 build 2004081808 under XP Pro SP1a here.
Severity: enhancement → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: access, clean-report, polish
Summary: "Edit link in composer" should be "E" not "I" → Accesskey of "Edit Link in New Composer" should be "E" not "i"
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: composer

Comment 2

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 3

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.