Closed Bug 67923 Opened 25 years ago Closed 25 years ago

cancel button alert cannot be accessed via keyboard navigation

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P2)

defect

Tracking

()

VERIFIED DUPLICATE of bug 84602
mozilla0.9.5

People

(Reporter: mmilli, Assigned: bugzilla)

References

(Blocks 1 open bug)

Details

(Keywords: platform-parity, Whiteboard: this is a bug on windows and linux (it's the correct behavior on mac))

From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (WinNT; I) BuildID: 20010201 while trying to cancel the deletion of a folder or mail message in mail, using the tab button on the keyboard to shift the focus to the cancel button( from the ok button) ,even though the cancel button gets selected the message still gets deleted when we press enter. Reproducible: Always Steps to Reproduce: 1.bring up the browser window 2.open a new mail window 3.select any folder/message(from thread window) either using mouse or keyboard. 4.and delete the message by any one of the following ways; (A)press del key on the keyboard (B)press the delete button on the toolbar (C)go to the edit menu and press the delete option 5.an alert appears saying "do you wish to delete the selected folder/message?" with 2 buttons 'ok' and 'cancel',and the ok button has the focus. 6. now press the tab key on the keyboard to shift the focus to the cancel button. 7. the cancel button gets selected Actual Results: On pressing enter key after the cancel button is selected via keyboard naviagtion(using the tab key) , the selected message /folder gets deleted. Expected Results: On pressing enter key after the cancel button is selected via keyboard naviagtion(using the tab key) , the selected message /folder should not be deleted and should be retained as it is.
not a mail news bug, a bug with the common dialog xul / js.
Component: Mail Window Front End → Browser-General
Product: MailNews → Browser
over to default owner.
Assignee: sspitzer → asa
QA Contact: esther → doronr
updating component and owner, passing the buck, bouncing, etc.
Assignee: asa → ben
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps: GUI Features
Ever confirmed: true
QA Contact: doronr → sairuh
->keybd nav
Assignee: ben → alecf
Component: XP Apps: GUI Features → Keyboard Navigation
Status: NEW → ASSIGNED
Keywords: access
Priority: -- → P2
Target Milestone: --- → mozilla0.9
Cc mpt (mpt: we've discussed what the enter key should do in dialogs before, in bug 63728). mmilli@in.ibm.com: pressing space (instead of enter) should activate the currently focused button. See also bug 59840 and bug 52751.
Yes, the reporter is correct. As described in bug 63728, when a command button is focused, that button temporarily takes over the Enter and Control+Enter keybindings (and the extra border) from the default button. When a control other than a button is focused, the Enter and Control+Enter keybindings should return to the default button.
Keywords: access
*** Bug 68675 has been marked as a duplicate of this bug. ***
*** Bug 68675 has been marked as a duplicate of this bug. ***
*** Bug 60801 has been marked as a duplicate of this bug. ***
Keywords: pp
OS: Windows NT → All
Hardware: PC → All
Whiteboard: this is a bug on windows and linux (it's the correct behavior on mac)
Bumping off the mozilla0.9 radar, I don't see any traction, and I don't think Alec will get to this for 0.9
Target Milestone: mozilla0.9 → ---
Keywords: mozilla0.9.1
futuring unless some accessability guy wants to grab this
Target Milestone: --- → Future
they call me accessibility guy
Assignee: alecf → blakeross
Status: ASSIGNED → NEW
I think it is the duplicate of the bug 52751.
Blocks: focusnav
usability/polish, 0.9.4.
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
*** This bug has been marked as a duplicate of 84602 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
vrfy dupe
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.