We are using radmenu on our website. However when using on mobile browser, radmenu dropdown can not be opened when touched to main menu items. We have searched over many forums, blogs. etc. We couldn't find any solution. We have updated the dll files to the final version but again it did not work.

 

What should we do to overcome this problem. Our mobile clients can not use the menu and we have to solve their problem immediately.

 

Thank you for your help.

 

Kind regards,

Hello Erthan,

I am afraid that we are not aware of such an issue. Do you replicate similar problematic behavior with our online demos:

http://demos.telerik.com/aspnet-ajax/menu/examples/overview/defaultcs.aspx

In addition, please demonstrate us the implementation of the RadMenu that you use at your end, so we could perform some local tests and try to pin down the reason for the experienced issue.

Regards,
Nencho
Telerik

Hello Nencho,

 The problems occur where it is an authorized section. That's why I have saved the page as an html file and get rid of much of the html parts unrelated with the problem leaving only the menu.

 Here it is: https://drive.google.com/open?id=0B5gQkiHExr_qWGZiWWxjU2IyQWc

The mobile test, as you will surely know, can be performed on Chrome Developer Tools by clicking mobile icon and refresh the page. Previewing on the mobile section it will be seen that dropdowns will not open by clicking menu items.

 I will be appreciated for your deal.

Kind regards.

 

Hi,

The link provided can not be accessed. In such case we would recommend submitting  a ticket about the issue and attach the page there.

Regards,
Plamen
Telerik

Hi,

 

I am very sorry about making the true the permission configurations. The document now can be accessed by everyone. But if you recommend me submitting a ticket, I will try to do that.

 

Thank you.

Hello Erhan,

I was able to download and test the referenced problematic behavior. However, we would need some more information, in order to determine the reason for the experienced issue, so please submit a support ticket. As I can see, there is an # appended at the end of the URL, which is causing the problematic behavior. But, as mentioned, we would need to revise your proper implementation, along with any custom (client-side) logic applied in your scenario.

Regards,
Nencho
Telerik