We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YUI uses 'TouchEvent.initTouchEvent' to simulate TouchEvent.
Currently Chrome is deprecating 'TouchEvent.initTouchEvent' and will remove in M53, developers are encouraged to use 'TouchEvent constructor' when available.
A monkey-patch for Y.Event.simulate could be
Y.Event.simulate
var oldSimulate = Y.Event.simulate; Y.Event.simulate = function(target, type, options) { if (type.indexOf("touch") == 0 && TouchEvent.length) { target.dispatchEvent(new TouchEvent(type, options)); } else { oldSimulate(target, type, options); } }
Another sample for 'TouchEvent constructor' can he found here (under Developer resources).
The text was updated successfully, but these errors were encountered:
Hi @choniong,
The YUI Library is EOL and won't be taking any additional changes.
If you need any assistance with patching a YUI fork, please feel free to reach out to me at @clarler.
Sorry, something went wrong.
@clarle Is this repo under development ? Are the issues being worked upon ?
Hi @AMaini503,
The YUI Library is no longer under active development, since Yahoo is no longer supporting YUI.
There's more information in the blog post below:
https://yahooeng.tumblr.com/post/96098168666/important-announcement-regarding-yui
Let me know if you have any other questions.
No branches or pull requests
YUI uses 'TouchEvent.initTouchEvent' to simulate TouchEvent.
Currently Chrome is deprecating 'TouchEvent.initTouchEvent' and will remove in M53, developers are encouraged to use 'TouchEvent constructor' when available.
A monkey-patch for
Y.Event.simulate
could beAnother sample for 'TouchEvent constructor' can he found here (under Developer resources).
The text was updated successfully, but these errors were encountered: