Dealing with iOS 8 Mobile Safari bugs?


(Sam Saffron) #8

Have you tried reporting this to apple, would be nice to track a ticket here.


#9

@eviltrout said he filled out a detailed bug report and I’m not knowledgeable enough about the problem to file out a duplicate one. I would suggest to update any existing bug reports that the issue is still broken in the latest beta.

Apple’s bug reporting system is closed so you can’t view other people’s bug reports unfortunately.


(Jeff Atwood) #10

@eviltrout can you provide a link here, and in the other topic, to the bug report you filled out so we can see if there is any activity and publicize it a bit more?


(John Oeffinger) #11

I’ll be happy to file a bug report if I have the information as well,


#12

We’d also need a sample project that can demonstrate the bug. I have read Apple puts more importance on the number of duplicate bug reports submitted for an issue.


(Robin Ward) #13

There don’t seem to be any public links to Safari bugs. However, they did close my bug as a duplicate of another which is a good sign that they are aware of it. Here’s their reply to me:

Hello Robin,

Engineering has determined that your bug report (18811562) is a duplicate of another issue (18559320) and will be closed.

The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.

An example of the duplicate section from the bug reporter user interface with your bug and the duplicate bug info is included below:

18811562 `position: fixed` is busted on mobile safari on iOS8

State: Closed                   Product:
Rank: No Value
---------------------------------------------------------------
Duplicate of 18559320 (Open/Closed)
---------------------------------------------------------------

They provide the bug ID that it is similar to 18559320 however that doesn’t link anywhere to review its status and what they’re doing about it.

In case you’re interested here’s my initial report:

Summary:
There are many issues with `position: fixed` in Mobile Safari on iOS 8 (and 8.1) that were not present in iOS7.

Here is a list that shows many of the issues we are seeing on our project in video form.

http://vimeo.com/user17710548/videos

In particular this behavior, where focusing on a fixed element is scrolling the page is very bothersome (http://vimeo.com/107938078).

Additionally we are seeing buttons that are not able to be clicked too, which is totally breaking our web app that used to work perfectly fine. (http://vimeo.com/107938076)

Steps to Reproduce:
Scrolling bug:

1. Create a text area in an position: fixed element on a page that you can scroll.
2. Click the text area



Expected Results:
Page should not scroll at all, as in iOS7 and other browsers.

Actual Results:
Page scrolls to top/bottom depending on where element is fixed

Version:
iOS 8.1

Notes:


Configuration:
iPad 4, iPad Air 2


Issues with the composer window on iPhone
(Jeff Atwood) #14

Thanks for that @eviltrout

So if you want to assist @JohnOeffinger75 and @BerryBlue and @olemoritz (or anyone else reading this, please) follow the repro steps above and file another bug with Apple.


(John Oeffinger) #15

I’ll file mine tomorrow - iPhone 6 latest build; iPad 3 latest build.


(Ionuț Staicu) #16

Hi guys, I have an idea that could make the whole thing more usable on iOS. Since i have some troubles on getting a working dev version, i can explain how to fix it. And there are two kind of fixes:

The most easiest way to fix is to add when compose window is visible:

body, html {height:100%; overflow:hidden}

Surely, this will make impossible to scroll between existing posts, but… at we will have a functional compose window.

The other solution would be a bit trickier to implement, but with good results. First, we need to move #reply-control div outside of #main div. Then, some CSS magic:

body, html {height:100%; overflow:hidden}
#main { height:100%; overflow:auto; -webkit-overflow-scrolling: touch; }
#reply-control { position:absolute }

In my quick tests (safari + GapDebug), everything play nicely.


(Jeff Atwood) #17

Depends how long these brutal iOS 8 Safari bugs go on…

Compose window is plenty functional on iPad, it’s just dialogs with the compose window open are 100% crazytown.

I have a method of adding images to posts on iPad that is weirder than a voodoo chicken sacrifice. I’m embarrassed to even describe it frankly.


(Sam Saffron) #18

I think we are ok with a PR that corrects works around the issue seeing IOS8 is so prevalent. Provided we can easily disable it when IOS fixes things.


(Ionuț Staicu) #19

Compose window to reply? Yes, functional. Compose window to create a new topic from the homepage? A total nightmare! It tries to scroll down to focus the editor, but then new posts loads, so will blur the editor and scroll more and so on.


(Jeff Atwood) #20

Hmm no repro, I am able to create topic fine on iPad 2 air. Landscape or portrait? I mostly use landscape.


(Ionuț Staicu) #21

You know how is said that an image worth 1000 words? Here are 600.000 words :smiley:

I’m on latest stable iOS - 8.1.3.


(Kane York) #22

Oh wow, that’s brutal.


(Jeff Atwood) #23

Yeah, I rarely use portrait. Try landscape as a workaround for now.


(Jeff Atwood) #24

Well I can confirm iOS 8.1.3 does not fix anything in this area. And 8.2 beta might not either as @BerryBlue noted. If this goes on, we will be forced to include iPad specific workarounds…


#25

I tried with iOS 8.3 beta (Posted: Feb 9, 2015) and the problem still exists unfortunately.


(Markus) #26

For now, I recommand Mercury browser. :ok_hand:
This works for me pretty smoothly.

http://mercury-browser.com


#27

It’s because it’s using a UIWebView to display web content which is different than what the Safari app uses to render web content.

iOS 8 introduced a new WKWebView which is the same as the Safari app.