Some dgrid Keyboard Listeners do not work in IE10/IE11 and Chrome 55.

[carter-erwin]

There seems to be in issue in IE10 and IE11 where the dojo.on(KeyDown) listeners which are set in "dgrid/Keyboard" are not registering properly when certain mixin combinations are used. This can be reproduced at http://dgrid.io/js/dgrid/demos/laboratory/ by enabling the "Keyboard" and "DnD" Grid Features. Other features, such as "Selection" can help to highlight the issue, but are not necessary.

[gerpres]

also ran into this issue. problem is, that in IE(11) the keyboard's mousedown-listener doesn't get called, and therefore the focus is not on the cell/row the keyboard's eventlistener would get called after the DnD event-handler which stops the event.

in chrome, the keyboard-mixin gets the event first, then the DnD

setting the focus works when clicking with the right-mouse-button - since the DnD code doesn't stop this kind of events.

has anybody any idea how how to solve that?

[kruthikavenkatathri]

I also see the same issue. Clearly, clicking on a row does not give focus to the row. But clicking on the dgrid-content or header gets focus. Does anyone have a fix for this?

[gerpres]

I just observed the same behavior in chrome 55.0.2883.87

[dylans]

I'm wondering if this is similar to https://bugs.dojotoolkit.org/ticket/18932 , which is basically a conflict between pointer events and traditional events.

[carter-erwin]

I was able to work around this issue using the below code on my grid widget, though I am not sure it is completely satisfactory, especially since @gerpres mentioned he is seeing this behavior on Chrome 55.0.2883.87.

// Behavior was only occurring in my testing with "pointerdown" events, so dispatch a "mousedown" event.
myGrid.dndSource.onMouseDown = function (e) {
    // This conditional statement avoids duplicate events.
    if (e.type !== "mousedown") {
        var mEvent = document.createEvent("MouseEvent");
        mEvent.initEvent("mousedown", true, true);
        e.target.dispatchEvent(mEvent);
    }
};

The goal of this workaround was to avoid modifying Dojo code, and avoid aspect-oriented solutions.

[msssk]

This works simply by luck in Firefox, and fails in other browsers due to the complexity of implementing drag and drop. dojo/dnd exerts a lot of control over pointer events, and in the case of nodes that are designated as DnD sources events can be canceled, causing problems for other code that is listening for them.

Firefox first calls the mousedown handler from dgrid/Keyboard which sets focus on the clicked node, then calls the DnD handler which cancels the event, but to no effect.

Chrome first calls the DnD handler which cancels the event and then dgrid/Keyboard's handler never gets called so focus is not set on the clicked node.

The recommended solution is to use specific DOM nodes as DnD sources, and limit what types of interactions are needed with those nodes. In the dgrid laboratory you can see this approach in action. If you look at the columns listed on the left, each has an icon to its left that is a DnD source - not only does this give a nice visual cue, but it also avoids conflicts between dojo/DnD and other code.

[gerpres]

any updates on this? in the meanwhile the problem go at least consistent across all browsers - ff69, chrome77, edge, IE11

[dylans]

@carter-erwin and @gerpres please verify that the fix in #1445 solves your issue, thanks!