Page 1 of 1
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 1:05 pm
by TonyS
A button has a click action applied simply to navigate to another page, but it requires 2 clicks. The first click refreshes the page and overrides visibility settings applied to other objects at service level and the second takes you to the target page.
Another one of those things that worked 3 months ago. What's changed?
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 1:20 pm
by TonyS
Ok it's all buttons that are doing this. All buttons have to be clicked twice. Is there a new setting somewhere?
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 1:27 pm
by TonyS
It's just buttons that have this issue a label or an image will go straight to target when clicked once. Appery is still as frustrating as I remember!
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 1:32 pm
by TonyS
Well well, it's fixed itself! Just suddenly works with one click?
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 1:37 pm
by Alena Prykhodko
Dear Tony,
If you test in browser you can try to clear cache, this can be a reason.
Glad it's working now.
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 2:35 pm
by TonyS
Thanks Alena,
I have numerous issues of this type, Currently the saved javascript is being ignored. Do you think it's my browser?
Button click navigate to requires 2 clicks why?
Posted: Fri Nov 13, 2015 2:45 pm
by TonyS
I have a bit of code on the landing page which I turn on and off to check the system.
//localStorage.clear();
Despite this being commented out it still clears the local storage every time. It didn't this morning?
Just in case it was a cache problem I tried using FF, appery is even slower and it still cleared the storage. Are you having problems with your system?
Button click navigate to requires 2 clicks why?
Posted: Sat Nov 14, 2015 11:57 am
by Illya Stepanov
Hi - Perhaps you clearing storage in some other part of your code?
Everything is up and running and we didn't experience any issues that you described above in our tests.