News for hackers. Stuff that matters.
Re:Complexities of an infinite scroller by tlammens on Monday July 11, 2016 @05:19AM (#12069837)
Is it me or is it impossible to scroll that page in Safari?
Re:Complexities of an infinite scroller by qwertyuiop924 on Monday July 11, 2016 @07:08AM (#12070236)
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"

Re:Complexities of an infinite scroller by Flow on Monday July 11, 2016 @08:39AM (#12070592)
They are apparently aware of it at least. https://news.ycombinator.com/item?id=11882964
Re:Complexities of an infinite scroller by kinlan on Monday July 11, 2016 @10:05AM (#12071081)
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)
Re:Complexities of an infinite scroller by Flow on Monday July 11, 2016 @12:12PM (#12072059)
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?

Re:Complexities of an infinite scroller by kinlan on Wednesday July 20, 2016 @01:06PM (#12130640)
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.
Re:Complexities of an infinite scroller by qwertyuiop924 on Tuesday July 12, 2016 @04:05PM (#12081933)
Sorry for the insult... but you guys really should have tested this across browsers before it even shipped.
Re:Complexities of an infinite scroller by asurma on Monday July 11, 2016 @11:44AM (#12071807)
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.

Re:Complexities of an infinite scroller by Flow on Monday July 11, 2016 @06:27AM (#12070078)
It's not just you. Safari 9.1.1 on El Capitan.
Re:Complexities of an infinite scroller by dzhiurgis on Monday July 11, 2016 @11:41AM (#12071782)
On one hand it is ironic, on another Safari still crashes after you peek into link. Half year later after the bug was introduced.
Re:Complexities of an infinite scroller by lazyjones on Monday July 11, 2016 @08:21AM (#12070506)
Same here, Safari 9.1.1 on OS X 10.11.5, uBlock and ABP installed.