This behaviour is usually iOS specific, other systems interpret these css rules in a bit different everyone: I'm looking into our Mobile Safari story and I wanted to ask for the detailed description of your use cases for iOS. Probably most typical use cases (as far as I can think of) are related to some invisible elements overlapping other elements and making it impossible to click on the overlapped element. Android/Windows/macOS works fine, but iOS requires this css rule for some reason. This is fixed by setting pointer-events: none on the hidden mobile menu element. But if you are running chrome, or safari on real iOS device, then the click will open the mobile menu. If you click on Domácí (see the picture below), then with chrome mobile emulation, you will be redirected to a section page Domácí (correct behaviour). (The fix will be probably released during next week, hopefully you can check it before that time). One current bug on our website, that is discoverable only on real iOS device (safari, or chrome) can be currently found on this page.
Testing on Android is much easier and faster.- They are usually some very specific (and kinda weird) use cases, typically on iOS devices. Once you have an account and you have set up Xcode with your certificates to enable device testing, you’ll want to open the Xcode project from platforms/ios/ and do your testing from Xcode. Unfortunately, this costs $99 per year (don’t blame us!). If you are building for iOS, you’ll need to sign up for an Apple Developer account to test as a native app on an iPhone or iPad. Since we are building a native (or “hybrid”) app, we can (and should!) test it as one. It is fine for small tests, but not recommended for more complex apps. They also have issues with the URL bars getting in the way, and some scrolling behavior is not the same as it is in the web view running in Cordova. For example, Chrome and Safari both listen for drag events on the sides of the app which let you switch between open tabs.
This is largely because the browser app is meant for browsing websites, so it often adds functionality that conflicts with your app. One problem with testing in a mobile browser is that it’s probably the furthest of the three options from the actual app experience. So, if our desktop is running a test server at 192.168.1.123:8000, we can just load that address into our mobile Chrome or Safari to test it. If you are using the local server method from the Desktop testing section and you are on the same network as the desktop computer, you can connect to the ip address of the desktop computer to test. Check out the Android docs for more info.
To do this with iOS 7 and OS X Mavericks, enable the Web Inspector option in the iOS Settings -> Safari -> Advanced section, and also enable the Developer Menu in the Advanced section of the Safari OS X settings.Īndroid apps supporting Android 4.4 or above can also use Chrome for remote debugging. First you have to enable the remote web inspector on both the device and Safari on desktop.
For OS X users, Safari on OS X can directly debug websites and simulator applications. You can also test the app directly in a mobile browser.
Which will update the ios specific project with the code from the Mobile browser testing