Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#17106 closed defect (fixed)

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

Reported by: bill Owned by: bill
Priority: undecided Milestone: 1.7.6
Component: Dijit Version: 1.9.0
Keywords: Cc:
Blocked By: Blocking:

Description

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.

Change History (6)

comment:1 Changed 7 years ago by bill

Resolution: fixed
Status: newclosed

In [31423]:

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

comment:2 Changed 6 years ago by bill

Milestone: tbd1.10

comment:3 Changed 6 years ago by Colin Snover <github.com@…>

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? 

comment:4 Changed 6 years ago by bill

Milestone: 1.101.9.2

comment:5 Changed 5 years ago by Bill Keese <bill@…>

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? 

comment:6 Changed 5 years ago by bill

Milestone: 1.9.21.7.6
Note: See TracTickets for help on using tickets.