Open Bug 22600 Opened 25 years ago Updated 2 years ago

Buttons that are triggered from keyboard should show visual feedback

Categories

(Core :: XUL, defect, P3)

defect

Tracking

()

People

(Reporter: hangas, Unassigned)

Details

(Whiteboard: ui)

In another bug elig pointed out this issue. We need to show the visual feedback for buttons that are activated from the keyboard, just as though it was clicked: ------- Additional Comments From elig@netscape.com 1999-12-23 13:39 ------- Using the 1999122308 build, the implementation deviates from the expected results (e.g. how default buttons behave in 4.x, or any other OS.) Specifically, upon pressing "Return" to auto-press "OK" to close a dialog, the dialog closes, without giving any visual feedback that the "OK" button was pushed. Instead, the button (and dialog's) behavior should be similar to if the user had pressed the "OK" button. hangas, please let me know if you'd like this side-issue split into a separate bug, with this one closed out. Thanks!
Status: NEW → ASSIGNED
Target Milestone: M14
Whiteboard: ui
["another bug" = broken out of bug #9635.]
Sending to you Dave, after our conversation about this bug.
Assignee: hangas → hyatt
Status: ASSIGNED → NEW
Target Milestone: M14
Accepting for M15. Don't believe this is a beta stopper, since the buttons only do this on one OS, the Mac.
Status: NEW → ASSIGNED
Target Milestone: M15
Yup. not a rush. Reducing severity to Minor.
Severity: normal → minor
Moving all UE/UI bugs to new component: User Interface: Design Feedback UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Target Milestone: M15 → M16
Target Milestone: M16 → M17
Mass moving M17 bugs to M18
Target Milestone: M17 → M18
Moving non-feedback items out of UI: DF in preparation for handover to mpt@mailandnews.com.
Component: User Interface: Design Feedback → XP Toolkit/Widgets
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
oh, well... ->future
Target Milestone: M21 → Future
I am not sure about the dialog applicability of this issue, but I have seen that builds have been triggering buttons from the keyboard just fine for me. As for dialogs, I have found that sequential alerts only allow you to click OK automatically on the first one, then after that the focus is lost into some far-off land (Mars?). I must click the second with the mouse. Just wanted to make sure this bug is still applicable and should it be closed invalid or something?
Not 'invalid', but perhaps wfm if it now behaves appropriately on all pertinent platforms.
QA Contact: elig → jrgm
--> default owner
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
Target Milestone: Future → ---
Assignee: jag → nobody
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.