Compatibility IE10 Touch

[Lorenzo Margola]

The new RadScheduler Q1 2013 will be full compatible with touch events like drag and grop appontements and long click for rad menu in IE10 Metro.

Now these events work only with iPad.

Thanks.  

[Ivan Zhekov]

Hi, Lorenzo.

The way most controls work is that we perform a check to see if a device is touch capable. Apparently, Windows 8 with IE10 fails that test and is not recognized as such.

I've logged the issue and awarded you some Telerik points for the bug report.

Regards,
Ivan Zhekov
the Telerik team

[Steve]

When will this be fixed? I'm developing a touch screen system now and everything is centered around a scheduler. Having the scheduler and all other controls, where necessary, support and work with a touchscreen is a must for me. The scheduler must support the drag and drop, using touch.

Right now, I'm evaluating Telerik controls suite (all the controls for all platforms). If this isn't working, then I must move on to another suite, such as Infragistics or Devexpress.

Again, when will this be fixed?

[OPL]

any news ? 

Thanks

[Ivan Zhekov]

Hi, all.

When we have any substantial progress on this, we'll update you.

For now I can repeat what's been said all over the groups: the issue lies a bit deeper and there is no quick fix. In short, we have TouchEvents and PointerEvents, both of which are candidate standards. Both behave differently and thus the issues.

Regards,
Ivan Zhekov
Telerik

[Steve]

Apparently not a priority. We're 10 months out from the initial reporting of this and the response from Telerik, and still nothing!

[Ivan Zhekov]

Hi guys,

Prior Microsoft's PointerEvents there were the TouchEvents, which are supported in all browsers but IE and vice versa for the PointerEvents.

It's worth nothing that attaching traditional handlers does not always work in touch or pointer; attaching touch events will not trigger pointer events; attaching pointer will not trigger touch. In other words we have to attach everything, which is not a good options because events tend to overlap in some areas. That's the main problem.

There are some other caveats, like IE 11 having different event names than IE 10, pointer events not truly working Windows7; IE 11 having issues with ASP.NET (as a whole) and so on and so forth.

So we gathered feedback, lots of it, we experimented and we think we have found a good solution. For Q1'14 we will try to implement an unified event handler and in Q2'14 to integrate it in as many controls as possible. If we succeed to implement it earlier we will notify you.


Best regards,
Ivan Zhekov
Telerik