We need to ensure the component library works and looks fine across browsers.
using playwright.webkit + iPhone device metrics. Why doesn't device emulation work for you? I.e.
#Mac mobile browser emulator Offline#
No, I didn't investigate into these details though.Īre you interested in Mobile Safari specifically, or running your page in WebView is sufficient? Are you interested in the tricky URL bar behavior?Īre you interested in testing WebViews in your apps?Īre you willing to give up some of the Playwright emulation capabilities (browser context isolation, timezone, locale, offline emulation, etc) to be able to perform simpler scripts with clicks, navigations, screenshots, etc?
real iOS device discrepancies to relay only on Xcode sure! Here it goes:ĭo you plan to use real device or Simulator?įor a real device, do you have it provisioned, unlocked and awaken? Why doesn't device emulation work for you? I.e.Are you willing to give up some of the Playwright emulation capabilities (browser context isolation, timezone, locale, offline emulation, etc) to be able to perform simpler scripts with clicks, navigations, screenshots, etc?.Are you interested in testing WebViews in your apps?.Are you interested in Mobile Safari specifically, or running your page in WebView is sufficient? Are you interested in the tricky URL bar behavior?.For a real device, do you have it provisioned, unlocked and awaken?.Do you plan to use real device or Simulator?.Answers to the following questions would help us a lot:
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. They are usually some very specific (and kinda weird) use cases, typically on iOS devices.
0 kommentar(er)
