dijit/focus.curNode not set when clicking tabIndex=-1 node

[bill]

dijit/focus has some code to ignore focus events on disabled elements. Not sure this is even necessary, but in any case it's having the side effect of also ignoring when elements with tabIndex=1 are clicked, and get focus.

This causes a failure in !BorderContainer_complex.html, although the test should probably be updated to not use dijit/focus as part of the test. But that's a separate issue. It also accounts for some test files doing a workaround of calling click() twice, and blaming it on a robot problem.

[bill]

In [31423]:

Set focus.curNode when clicking non-disabled tabIndex=-1 element, fixes #17106 !strict. Tested on IE8, IE10, chrome.

[Colin Snover <[email protected]…>]

In 1a799036daa8543e27921748e378de58f6e22343/dijit:

Error: Processor CommitTicketReference failed

Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

[Bill Keese <[email protected]…>]

In a593ea271433673d786ccf9e010463362104baef/dijit:

Error: Processor CommitTicketReference failed

Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled?