Hello,
I cannot scroll the grid by touch when using JsRender Integration.
I tested with a Micosoft Surface 2.
You can use the JsRender Integration demo to reproduce the issue.
Best regards,
Joern
Hello Joern,
Thank you for your patience!
Currently there is no WinJS support, in other words there wont be any service releases that will contain any fix regarding this issue. According our developers there is some jQuery problem with the jQuery append method. This is a possible workaround for this issue (see the link below):
http://stackoverflow.com/questions/13139418/jquery-append-type-input-and-windows-store-app-html-css-js
Wrap the part that is throwing the exception with MSApp.execUnsafeLocalFunction.
If there is something else that I could help you with, contact me.
thanks for the Feedback:
1. How is this bug related to WinJS?
Just go to the Ignite UI Demo with any Windows 8.1 tablet with touch and it does not scroll. The problem is with IE11 and touch on a web page. (I have not checked Windows 8 with IE 10 and touch.)
2. Surface device support is advertised by Infragistics
As said above - the bug is not related to WinJS - but I do plan to use Ignite UI with WinJS.
Here is the text from the Infragistics store:
"Create modern, responsive desktop browser-based apps & mobile apps With MVC or HTML 5, CSS3 and JavaScript to deliver line ot business Solutions that look, teel and behave just like device-native apps, without learning multiple languages or trameworks From the iPad to Phone, Android, Windows Phone and the Surface tablet, Ignite Ul bridges the path to multi-device development. And the apps you build can be published to the App stores."
As you can see the Surface is mentioned along with iPad, etc. and it does say that the apps can be published to the App stores.
The only reason I bought Ignite UI and not another framework was the Surface (WinJS / WinRT) support. If you look into the source code of the igGrid you will see that WinJS support is implemented. There is special WinJS code and calls to MSApp.execUnsafeLocalFunction. Why is it there?
Your workaround is not usable because that would mean that I have to patch all of the Ignite UI source code.