Open Bug 191801 Opened 22 years ago Updated 15 years ago

[mailviews] accesskeys don't work in Customize Message Views/Message View Setup

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: nbaca, Unassigned)

References

(Blocks 1 open bug)

Details

Trunk build 2003-02-03: WinMe

Overview: In the Message View Setup dialog, Alt+E should place the cursor in the
"Message view name" text box.

Steps to reproduce:
1. In the View drop down select Customize
2. Select the New button
3. Move the focus to any element (except for the "Message view name" text box
4. Alt+E

Actual Results: Nothing happens
Expected Results: The cursor should move to the "Message view name" box
Blocks: mailviews
The hotkey to refocus to the MailView was changed to Alt+I.  This works fine in 
Mozilla 1.6 (at least, under Win2K).

=>WFM

Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Reopening -- I am an idiot who cannot read.  This is about the Message View name 
box in the Setup dialog.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Status: REOPENED → NEW
(In reply to comment #2)
> Reopening -- I am an idiot who cannot read.  This is about the Message View
> name 
> box in the Setup dialog.

what setup dialog?
and is this something other than front end? eg. prefs?

(In reply to comment #3)
 
> what setup dialog?

Follow the instructions in comment 0.


> and is this something other than front end? eg. prefs?

Front-end in my book.
In fact, none of the accesskeys in Customize Message Views/Message View Setup work at all...
Summary: [mailviews] Alt+E doesn't move cursor to "Message view name" box → [mailviews] accesskeys don't work in Customize Message Views/Message View Setup
OS: Windows ME → All
Hardware: PC → All
Blocks: 279001
No longer blocks: 279001
Assignee: mail → nobody
Depends on: 400854
QA Contact: esther → message-display
You need to log in before you can comment on or make changes to this bug.