|
|
Rank: Member
Groups: Member
Joined: 6/23/2010
Posts: 18
|
We have recently upgraded to EO.Web Controls Suite (2013) and everything went pretty smoothly except for the menu. When using Safari IOS, we've noticed that the system always pick the first option in the submenu, not waiting for user to pick, and invoke the page. We have tried Chrome in IOS as well with the same result. Is there a way to get around this issue?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Thanks for posting in the forum. We will look into this and get back to you as soon as possible.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
We tested on IOS 7.0.2 and we have not been able to reproduce this problem. We tested both with the built-in Safari browser and Google Chrome browser. Both works fine. You may want to test from another device to see if you see the same problems.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/23/2010
Posts: 18
|
That's the problem. It is running properly in IE 8,9,10, Chrome, Firefox, Opera in WINTEL environment. The order version (EO 2009) works fine in IOS as well. THe problem perks up with our new version using EO 2013 and only in IOS.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
I am not sure what to tell you. We tested 2013 on IOS and it worked fine here. In order for us to investigate a problem, we have to be able to duplicate it first. If you have the page online we will be happy to try it here from an IOS device as well.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/23/2010
Posts: 18
|
That will be great. Can you send me an email link so that I can send you the URL and the account information? It is a protected environment.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Please see your private message for the email address.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
We have looked into your page. The root of the problem is you have set the NavigateUrl for both the top level menu item, as well as the first child menu item to the target page Url. As a result, when you touch the top level menu item, which is interpreted as a click, would go to the target Url directly. This would not be an issue on a non touch screen device because the sub menu would open on mouse over, not on mouse click. However in a touch device you should avoid setting the top level item's NavigateUrl. Doing so would render the sub menu items useless.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/23/2010
Posts: 18
|
Thank you. We have changed the data retrieval procedure for the menu build to eliminate the NavigateURL for the top level menu item and the problem is resolved.
Thanks for checking it out and the advice provided.
|
|