NEW 146067
iPhone 6 plus landscape view with url/tab bar showing: fixed element's tap regions not updated
https://bugs.webkit.org/show_bug.cgi?id=146067
Summary iPhone 6 plus landscape view with url/tab bar showing: fixed element's tap re...
Mike
Reported 2015-06-17 09:38:59 PDT
Overview: When in landscape mode on iPhone 6 plus (with the iPad-like URL and tab bar), touch targets (menu links, logos, buttons) on elements in a fixed position parent element are not updated when the tab bar UI is displaying, after being hidden after first page load. Steps to reproduce: 1) Visit http://www.apple.com/watch/ on iPhone 6 plus in landscape orientation. 2) Scrolling down, a white nav bar will become fixed to the top of the viewport, all buttons in the nav work as expected. 3) Tap the very top of the screen to summon the address bar and tabs UI. The fixed nav bar moves down some, and the touch targets for the buttons in the nav no longer align with the rendered nav. They stayed where they were before the tabs UI was moved in. Scrolling up the page, keeping the tabs UI visible, properly moves the fixed nav, but the touch targets remain unmoved. Scrolling down again hides the tabs UI, and updates the position of the touch targets, returning to properly functioning buttons. Actual Results: The touch targets do not follow their related elements when the tabs bar is showing and instead remain stuck where they were before the tabs bar was showing. Desired Results: The touch targets should follow their related elements whether the tabs bar is showing or not. Platform: iPhone 6 plus on iOS 8.3 (12F70) public release
Attachments
Simon Fraser (smfr)
Comment 1 2015-06-18 19:02:31 PDT
Can you test the iOS 9 beta build please?
Mike
Comment 2 2015-06-18 19:52:57 PDT
I don't have a paid dev account, so I'd have to wait until the public beta, if I get in.
Mike
Comment 3 2015-07-10 20:33:55 PDT
This issue remains in iOS 9 beta 3
Roger Taylor
Comment 4 2017-04-19 07:27:42 PDT
This issue still exists, also appears on iPhone 7 Plus iOS 10.
Simon Fraser (smfr)
Comment 5 2017-04-19 15:41:14 PDT
Are you sure? I fixed an issue like this in 10.3.
Note You need to log in before you can comment on or make changes to this bug.