ComboButton: disabled can still get focus

[bill]

On test_Button.html in FF, in the console do:

dijit.byId("save").attr("disabled", true);

Then click the disabled button. It still gets focus. Tabbing from previous buttons also sets a tab stop there.

I'll check in tests for this into Button_a11y.html, commented out. Uncomment when this is fixed.

[Douglas Hays]

Hopefully this s related: the disabled ComboBox? in test_ComboBox.html can be focused and shows the dotted outline (I'm testing with FF2 on WinXP). Looks like 2 issues: 1) this._focused=true (focus manager problem), and 2) in dijit.css, dijitDisabled disables the cursor but not the outline CSS attribute.

[Becky Gibson]

Why is this accessibility? Setting back to dijit.

[bill]

See #8595, probably the root cause of this.

[bill]

Changed my mind, will fix this for 1.5.

[bill]

(In [22011]) Fixes so that disabled widgets don't get focus by mouse or keyboard:

• Made focus manager ignore click events on disabled widgets. It still responds to actual focus events so that Menu still works (which focuses the disabled MenuItems). Clicking a disabled dijit.form.Button in an enabled TabContainer will call onFocus() on the TabContainer (and the ContentPane) but not the Button.
• Fixed _FormWidget._setDisabledAttr() to set/remove tabIndex on all focusable nodes. Usually only focusNode is focusable, but ComboButton has two focusable nodes. Disabling a widget now sets tabIndex=-1 on nodes like <button> but removes tabIndex on nodes like <div>.
• Added new method dijit.hasDefaultTabStop() to support above code.

The only remaining problem is webkit, where clicking widgets still gives them focus, but this is a webkit bug that doesn't seem feasible to workaround. I did add workaround code for webkit so at least keyboard works correctly, by using tabIndex=-1 instead of removing tabIndex (see #11064 for details).

Fixes #8903, #8923, #8595, #11053, refs #11064 !strict.