Hacker News Reader

Comment by MBCook | Hacker News Reader

It wasn't a bug in Safari, that was simply the way the scrolling behavior was implemented in iframes.

It was still there choice to deploy using iframes knowing that that was the way it felt. They could've use JavaScript to load the contents into a div or simply pushed so far users to a page that had nothing but the AMP content on it.

They left it severely sub optimal and decided that was good enough… making google significantly more annoying to use on iOS than what it was before.

That was the choice they made and stuck too. No options to turn it off, no options to do it a different way; you just get stuck with it.

View on HN

It isn't related to iframes directly. Iframes in mobile Safari are never scrollable. The div thing you suggest would have the same issue. If you are a web developer you likely have built a website that has this issue.

Ah. I mostly do back end work, the front and stuff I do we haven't spent any time on optimizing it for mobile, only desktop browsers. I'm not familiar with the quirks of mobile browsers. I only know the iframes scroll oddly because I've been told that was why AMP pages feel weird on iOS here on hacker news before.

If you haven't done much front-end word, let alone handled quirks of mobile browsers, consider listening to other people on this thread instead of arrogantly pontificating all around.

So because I don't know the intarcacies of mobile web development I don't get to have an opinion on the UX of a website I use every day?

So my top-of-the-head guess of something that might avoid it based on what I thought the problem was from other HN discussions wasn't right. What a sin.

That doesn't invalidate my experience or frustration as an end user.

>It was still there choice to deploy using iframes knowing that that was the way it felt.

So you're blaming Google for not writing around an edge case bug that exists only on one platform?

Reply on news.ycombinator.com