4 ms·

Is it me or is it impossible to scroll that page in Safari?

Flow 10y ago
It's not just you. Safari 9.1.1 on El Capitan.
qwertyuiop924 10y ago
Gee. Google code not working on non-google browsers. What a surprise. Speaking as a firefox user, I'm lucky if google docs even loads, let alone works properly. Yet a another example of google talking out of their ass about "supporting web standards"
- Flow 10y ago
  They are apparently aware of it at least. https://news.ycombinator.com/item?id=11882964 https://news.ycombinator.com/item?id=11882964
  - kinlan 10y ago
    We are aware, and it certainly wasn't intentional. Waiting for fix in our impl of Material Design Lite (ironically before we move off it)
    - Flow 10y ago
      What are you gaining by replacing the native scroll functionality? Are you trying to add "standard Android scrolling inertia" or something? I mean you must be trying to change something, or will I not notice it when it's working?
      - kinlan 10y ago
        We didn't replace anything, there seems to be a bug in Safari that we have to work around with a translatez() hack.. should be fixed now.
    - qwertyuiop924 10y ago
      Sorry for the insult... but you guys really should have tested this across browsers before it even shipped.
lazyjones 10y ago
Same here, Safari 9.1.1 on OS X 10.11.5, uBlock and ABP installed.
dzhiurgis 10y ago
On one hand it is ironic, on another Safari still crashes after you peek into link. Half year later after the bug was introduced.
asurma 10y ago
Yes, sorry about that. We currently can’t scroll on the body element due to a limitation in Chrome, where an empty body layer is not being optimized. So we are scrolling in an element. However, that usually requires setting `-webkit-overflow-scrolling: touch;` so that you can scroll as usual on iOS. However, that in turn has a lot of hidden implications (like squashing layers, etc. Don’t know the details right now), that make performance suffer greatly. AFAIK, Safari will change their scroll-on-element behavior. Let’s see what the future brings.

Flow 10y ago

It's not just you. Safari 9.1.1 on El Capitan.

Gee. Google code not working on non-google browsers. What a surprise. Speaking as a firefox user, I'm lucky if google docs even loads, let alone works properly. Yet a another example of google talking out of their ass about "supporting web standards"

Flow 10y ago
They are apparently aware of it at least. https://news.ycombinator.com/item?id=11882964 https://news.ycombinator.com/item?id=11882964
- kinlan 10y ago
  We are aware, and it certainly wasn't intentional. Waiting for fix in our impl of Material Design Lite (ironically before we move off it)
  - Flow 10y ago
    What are you gaining by replacing the native scroll functionality? Are you trying to add "standard Android scrolling inertia" or something? I mean you must be trying to change something, or will I not notice it when it's working?
    - kinlan 10y ago
      We didn't replace anything, there seems to be a bug in Safari that we have to work around with a translatez() hack.. should be fixed now.
  - qwertyuiop924 10y ago
    Sorry for the insult... but you guys really should have tested this across browsers before it even shipped.

lazyjones 10y ago

Same here, Safari 9.1.1 on OS X 10.11.5, uBlock and ABP installed.

dzhiurgis 10y ago

On one hand it is ironic, on another Safari still crashes after you peek into link. Half year later after the bug was introduced.

asurma 10y ago

Yes, sorry about that. We currently can’t scroll on the body element due to a limitation in Chrome, where an empty body layer is not being optimized. So we are scrolling in an element. However, that usually requires setting `-webkit-overflow-scrolling: touch;` so that you can scroll as usual on iOS. However, that in turn has a lot of hidden implications (like squashing layers, etc. Don’t know the details right now), that make performance suffer greatly. AFAIK, Safari will change their scroll-on-element behavior. Let’s see what the future brings.