Closed Bug 114072 Opened 23 years ago Closed 14 years ago

Import Wizard, second screen: No visibility in access of the first field

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: olgam, Unassigned)

References

Details

(Keywords: access, Whiteboard: imp-mail)

Build 2001-12-07

Overview: No visibility when use Tab to move focus. Initially it looked that we 
don't have access to first field ("Please select the program
from which you would like to import:"), then I tried to use arrow keys when
hoped that I am in this field. Got first item highlighted and could use arrow
key for selection. But it is not intuitive for a regular user.

Steps to reproduce: from 3-pane: File|Import. Click on 'Next' button.
Get second dialog. Try to select a program to import by using only keyboard.

Actual Results: No visibility of keyboard accessing to first field.

Expected Results: keyboard access and visibility of accessing to all fields.
Keywords: access, ui
QA Contact: esther → olgam
Assignee: sspitzer → ssu
Keywords: nsbeta1
reassigning to ssu.
Updating multiple bugs. This is a valid UI issue. Would be nice to have it fixed
if time allows.
Status: NEW → ASSIGNED
Keywords: nsbeta1nsbeta1-
Whiteboard: imp-mail
Blocks: 126323
olga, it appears to be another caret focus textbox issue here.. see bug 103197,
bug 123216, bug 100130 and bug 82534.
It's great information - helps to understand the issue. It's one more case - and
fix is coming (bug 126850), so let's wait and then verify. 
Blocks: 154249
I remove nsbeta1- keyword - it was for MachV.
Keywords: nsbeta1-
Now I add 'nsbeta1' keyword for Buffy. Sorry, it's faster to edit multiple bugs
at once than manually go to each and remove minus.
Keywords: nsbeta1
Trunk build 2003-01-07: WinMe
Similar problems are present:

1. From the 3pane mail window, Alt+T
2. "I" for Import
3. Tab to the Next button and "Communicator 4.x" is highlighted

Actual Results:
a. Press Enter and it displays the "Select address book file" dialog as expected
b. try steps 1-3 again but this time select the down arrow key and focus goes
from the Next button to the Cancel button.

Keep pressing the down arrow key and now it cycles through all the listed
application but now it does not highlight the bottom buttons. To access the
bottom buttons (i.e. Back, Next, Cancel) I have to Tab as expected. So it's
strange that initially you have to use the down arrow key to get access to this
window and then eventually all the keys work as they should.

Expected Results:
For Actual Results "b." I would expect the highlight from Communicator 4.x to
move to the next listed application which is Eudora. I would not expect the down
arrow key to move to the Cancel button. 


QA Contact: olgam → nbaca
Mail triage team: nsbeta1-
Keywords: nsbeta1-
Keywords: nsbeta1
Product: Browser → Seamonkey
Assignee: ssu0262 → mail
Status: ASSIGNED → NEW
QA Contact: nbaca
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.