I tried this example in my Cordova app with onsen-ui and ui-router
UI-Router with Onsen-UI
http://codepen.io/argelius/pen/WveKKO
Everything works fine till I click the Android back button from page 2 or page 3, the transition won't work any more.
Is it possible to make the above sample working with Android back button?
Thanks.
Related
I am using Xamarin Forms with Master Details Page and TabbedPage. There seems to be a bug that I cannot understand or fix. On the MasterDetail Page, at the bottom quarter of the page, no clickevents are being fired. In other words, that part of the screen seems unclickable. It works fine on Android but on all iOS devices, the bottom quarter of the MasterDetail Page (that is just above the Bottom Tab) seems Unclickable.
I tried removing all content from the page and just add a simple button in that area and that too didn't work. It really seems frustrating.
On simulator as well as real app deployment, it doesn't work.
I use the Navigating event of my WebView to treat some urls in a special way. If the web page has an iframe, the navigating event in Android is unfortunately not fired (iOS works fine).
Do you have an idea how to solve this problem?
Until now I found a similiar unanswered question in the Xamarin Forum.
Im using prism with my xamarin forms application. i use master detail with the exact structure that you used but when i change detail page my back button wont work and when i click on back button in android it just close the app. and also the back button in toolbar wont show either. how can i fix this?
this picture belongs to time that i've changed the detail page that you can see there is no back button there
Version with issue: 7.0.0.396
Xamarin.Forms version: 3.0.0.482510
IDE: VS 15.7.1
enter image description here
I have tried to get the data-role="backbutton" kendo mobile ui feature to work but I am having issues. When testing the app on my iPhone 4 I get stuck in my app because the back button breaks the UX.
What happens is that when I am testing, I click heaps of back buttons (as they are used quite heavily in my app) and then randomly one decides to slide the previous view into the screen but only goes halfway and then snaps back (or some other type of visual glitch occurs). Then after that, all my navigation breaks down and I get stuck in the last view that I was in. Or better yet the links go to places that they are not supposed to. My tab bar does not work and either do links in the header. I have to exit the app completely, remove it from operating and try again. Seriously something wrong going on here.
I have tried to programatically add the back button by following the Kendo UI documentation but that does not work either. I am left with a button that does absolutely nothing when clicked - it may not even solve the issue anyway. I have looked using developer console in Google Chrome but I can't see any obvious issues.
Has anyone using Kendo Mobile UI experienced this issue before?
I downloaded the latest release of the Kendo UI build and the problem seems to have been resolved. Surprising! I assumed the Kendo framework was a bit more mature to be experiencing such a big issue. It was occurring when using slide transitions in navigation. Here is a link to the bug post on Github https://github.com/telerik/kendo-ui-core/issues/66
I'm using sencha touch 2.3.1
I have a button on a page and clicking it will open a new page (above the current page).
But when I click/tap on the new page in the region where the button is ( in the original page ) , the button is still getting clicked.
And a new view of the same page is being opened.
I'm facing this problem only in windows phone, it works fine in android, IOS and all browsers (including IE) through IIS. I'm using the tap event for this button.
Please help me resolve this.
Thank you.
Sounds like your issue is similar to this bug I've reported a while back:
http://www.sencha.com/forum/showthread.php?237550-2.1-Tap-event-is-passed-to-the-textfield-in-new-view
The workaround which has been working for me is adding e.stopEvent(); to the tap handler of the component the user is tapping on.