problems when faux mousedown appears on node behind touchend node

[wkeese]

(I know we discussed this over email but I'm filing a ticket before I forget.)

See dojo/dojo@6117ba1, and https://bugs.dojotoolkit.org/ticket/15878#comment:24.

The problem happens for example when there is a <button> behind a Menu. The user clicks a menu item, which then closes the menu, and iOS sends a mousedown/mouseup/click event to the <button> rather than to the menu item.

It might also happen when tapping causes a scroll, for example opening an accordion container pane.

I don't have a test case offhand nor do I remember which platform this occurred, but I think it was iOS6. Perhaps @edurocher can help more, since it was his patch.

[edurocher]

IIRC this occurred on dijit widgets on iPad, probably iOS6, and the test case was https://github.com/dojo/dijit/blob/master/tests/mobile.html I think, but I don't remember the precise scenario. The real problem IIRC was not the mousedown/up themselves, but the fact that with dojo/touch they arrived in a completely different order, e.g. click then mousedown/up, whereas the natural order is mousedown/up then click.

My patch just suppressed the native mousedown/up events fired after a synthetic click event, because it seemed unrealistic to modify the dijit code for this. A different solution would have been to also send synthetic mouseup/down events, so as to mimic the native order, but again that seemed complex and suppressing these events worked fine.

[wkeese]

I made a simpler (i.e. pure HTML/CSS) test case in https://bugs.dojotoolkit.org/attachment/ticket/17816/popup-ios-bug.html.