Closed mixed closed 7 years ago
The transform issue is caused by jQuery ~3.1 bug and jQuery foundation has plan to fix this next release(3.2).
I think it would be better not to fix it.
In case of eg.Flicking error, occurs because of comparison of element's style existence. I found something weird on attribute setting on jQuery 3.0, but I'm not really sure that is jQuery's problem.
It behaves not removing attribute itself. Normally, executing below code it removes.
// expected behavior is removing 'style' attribute
$("#some").attr("style", null);
But, in the code example that I made, after creating MovableCoord instance, it doesn't remove attribute, just removes its value only.
I'm suspicious on Hammer.js's code, but to solve this issue, I'll try to change comparison condition.
Bear in mind, that jQuery slim
version excludes below functionalities, which effects (ex. timing function $.easing) used by egjs, make difficult to use slim version.
Slim Build
All in all, it excludes ajax, effects, and currently deprecated code. https://blog.jquery.com/2016/06/09/jquery-3-0-final-released/
I've just checked unit test on Safari/FireFox/Chrome on MAC OSX.
Unit Test Failed Count