Opened 14 years ago
Closed 14 years ago
#4428 closed defect (fixed)
Disabled buttons on a toolbar should not be in the navigation order
| Reported by: | simonjb | Owned by: | simonjb |
|---|---|---|---|
| Priority: | high | Milestone: | 1.0 |
| Component: | Accessibility | Version: | 0.9 |
| Keywords: | Cc: | Becky Gibson | |
| Blocked By: | Blocking: |
Description
Disabled buttons are removed from the tab order on HTML pages. To be consistent, disabled buttons should be removed from the navigation order on a toolbar. We will need to handle buttons that change their enabled/disabled state after the toolbar has been initialised. For example, the undo button on the editor toolbar becomes enabled when there are changes to be undone and it becomes disabled when there are not.
Attachments (2)
Change History (5)
comment:1 Changed 14 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 14 years ago by
Changed 14 years ago by
| Attachment: | DisabledToolbarButtons_UNFINISHED_2.diff added |
|---|
Changed 14 years ago by
| Attachment: | DisabledToolbarButtons_UNFINISHED_3.diff added |
|---|
comment:3 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
(In [10538]) Do not focus disabled widgets. Changed the management of tabIndex: focus is now handled by the container which then passes focus on to its first focusable child. I also took the opportunity of switching to some more compact code syntax: dojo.forEach, this.connect (thanks Bill!) Fixes #4428.
Discussed on #dojo-meeting 2007-09-17. We will not focus any disabled widgets (including disabled menu items).