website: scrolling doesn't work on iOS

[adg]

"You can't zoom.  (You "can", but then you can't scroll.)  If you don't
zoom, you can scroll, but it's oddly slow and doesn't track your finger correctly.  (At
a guess the scrolling is emulated in Javascript?)  And for me at least, if I can't zoom,
it's unreadable on that platform."

[kisielk]

Comment 1:

More specifically in my case (iPhone 4S, iOS 6) you can zoom in and out though it is
choppy. Once the scrolling proceeds extremely slowly, it takes many swipes just to move
a few lines of text.

[minux]

Comment 2:

seems to have something to do with the floating topbar.
iirc, i started experience slow scroll soon after floating topbar feature was added.

[minux]

Comment 3:

confirmed. i disabled fixed position css rule of div.topbar and div.page,
and then the problem just went away.
we need to disable the floating topbar.for mobilesafari.

[adg]

Comment 4:

Can anyone propose a means of reliably detecting mobile safari? Do we need to use
JavaScript, or is there another way?

[gopherbot]

Comment 5 by andybons@chromium.org:

My unsolicited advice is to not target specific OSes/versions since it's likely that
this is also broken on some Android distros as well (it's a webkit issue, not an OS
one). That being said, there are many reliable ways to detect mobile safari.
Since this has bitten me as well (reading the spec on my iPad) I'm more than happy to
help. The top-level goal being that we find a solution that doesn't rely on browser
checks to work everywhere.
Let me know if you'd like me to start working on a patch.

[gopherbot]

Comment 6 by andybons@chromium.org:

The top bar being fixed isn't the issue. It's the styling of the body element itself
that's causing the jitters.
in doc/style.css:537 change the 'position' property of div#page.wide to be 'relative'
and not 'fixed'. Tested it locally with Mobile Safari on iOS 6 (tablet and phone) and it
scrolls smooth.
In terms of zooming on the phone, there's a bit more CSS to that in order to make it
look nice, but this solves the major pain-point.

[adg]

Comment 7:

This issue was closed by revision c128474.

Status changed to Fixed.