[Draggable onClick issues on Chrome 55 (touch)]

Hi Jack,

 

I'm sorry to keep bugging you with this, but we found a few more edge cases:

 

1. The fix doesn't seem to work if allowNativeTouchScrolling is true - we still get both the MouseEvent and the PointerEvent. This is not huge a problem for us, I just wanted to let you know about this issue.

 

2. There is still something wrong with the events, although I'm still trying to figure out a test case. However, you can see here -

See the Pen PWGZeW by nyordanov (@nyordanov) on CodePen

- that the inner link becomes focused when you tap on "Open submenu".

[Draggable onClick issues on Chrome 55 (touch)]

I'm afraid that this is still broken:

See the Pen RKPMvZ by nyordanov (@nyordanov) on CodePen

The problem only appears if you tap on "Open submenu". Regular mouse clicks are fine. Emulated touch events are also broken, so you can use that for testing.

[Draggable onClick issues on Chrome 55 (touch)]

Hi,

 

I originally posted this as a reply to another topic, but it has since been marked as "Answered" and it got buried. So, I figure it's best to post a new topic for this issue.

 

Essentially, event.preventDefault() in Draggable's onClick callback no longer works in Chrome 55.

 

The problem only appears on Chrome 55 with touch events (regular mouse clicks are fine). I've created a minimal demo + instructions for reproducing the problem here:

 

Our current workaround is to add a 100ms delay between the click and the opening of the submenu, but we'd be grateful if you could offer a permanent solution.

See the Pen qRBwEV by nyordanov (@nyordanov) on CodePen

[Draggable Chrome]

Hi, we have encountered a related issue.

 

This one only happens on Chrome 55 with touch events (regular mouse clicks are fine). I've created a minimal demo + instructions for reproducing the problem here:

See the Pen qRBwEV by nyordanov (@nyordanov) on CodePen

 

Our current workaround is to add a 100ms delay between the click and the opening of the submenu, but we'd be grateful if you could offer a permanent solution.

[Sandboxing Draggable]

Thanks Jack, it works now.

[Sandboxing Draggable]

Sorry, it doesn't work with CSSPlugin either - http://vamtam.com/throwprops-test/

 

I've even tried using TweenMax, but this also didn't help.

[Sandboxing Draggable]

Hi again,

 

I've done some additional tests and I have a basic demo of the problem here: http://vamtam.com/throwprops-test/ (check the console)

 

I now believe that there's something wrong with the sandboxing of Draggable. Right now I only have Draggable, ThrowPropsPlugin and TweenLite on the test page, Modernizr is not involved. The order of the scripts is the same as in this codepen -

See the Pen zDwEk by GreenSock (@GreenSock) on CodePen

.

 

Is it not possible to sandbox Draggable similar to the method recommended here, for example: http://greensock.com/forums/topic/9881-avoid-multiple-loaded-tweenmax-and-tweenlite/?

[Sandboxing Draggable]

Suppose that I have the following code:

 

window.mygs = window.GreenSockGlobals = {};

Modernizr.load( [ {    load: [

        'TweenLite.js',

        'ThrowPropsPlugin.js',

        'CSSPlugin.js',

        'Draggable.js',

    ],

    complete: function () {

        window.GreenSockGlobals = window._gsQueue = window._gsDefine = null; // from TweenLite.js line 67

        

        window.mygs.Draggable(...);

    }

} ] );

 

 

When I run it, I get this error:

 

Uncaught TypeError: Cannot read property 'greensock' of undefined                Draggable.js:795

 

What am I doing wrong? Is it possible to load a sandboxed version of GSAP asynchronously? I only need it after the page has loaded, so I'd prefer to load it asynchronously.

 

Thank you.