Hacker News Reader

Comment by tedmiston | Hacker News Reader

They do not work as well on iOS. Two examples of this are "scroll to top" by tapping the title bar is completely broken under AMP. The other is that Safari Reader is mostly broken under AMP. That said, the experience with super fast, virtually instant loads, is great, and I think these are definitely kinks that can be worked out.

I'm just confused why they made it through to consumer release without someone else questioning them. These are major features of the most popular browser on [one of the two] most popular mobile OS that Google is choosing to break.

Edit: Added "[one of the two]"

View on HN

> "scroll to top" by tapping the title bar is completely broken

This is because the scrolling is in a container rather than the body. It's a tough problem on many mobile pages using sliding drawers for example, which rely on overflow based scrolling. There's no event, that I'm aware of, for a web app to listen for for tapping that UI element on iOS.

Ultimately, it's a non-standard convenience introduced on iOS only. Maybe someone else here has solved this :)

I'm not sure how this is non-standard.

On iOS, there are various conventions that apps generally follow. On a list item you can swipe from right-to-left to bring up a Delete option. On a list of stuff you can tap at the top of the screen to scroll to the top. These are standard things in the iOS ecosystem.

A good parallel outside of iOS would be the pervasive use of right-click to bring up a context menu in Windows or the convention of having "--help" show help text in Linux.

Non-standard with respect to what? It's used in every Apple app, as well as tons of third party apps — Facebook, Instagram, and Gmail to name a few.

" the most popular mobile OS "

iOS at 23% and falling...

http://bgr.com/2016/06/02/apples-mobile-market-share-sees-bi...

A cursory look at those stats should tell you they're bogus. Going from 32% to 23% market share (about a 30% decline) in two months is not even remotely likely.

I just edited it to say one of the two most popular to avoid going there. I don't think it changes my point.

Doesn't it? I think it straight up answers your question.

The point I was trying to make was that iOS, and Safari on iOS, has a massive, massive user base. Throwing #1 vs #2 into the mix is distracting from that point.

Reply on news.ycombinator.com