> You deployed something that worked horribly on iOS
Except that thing was a bug in Safari. They used perfectly valid plain HTML without any hacks or JS.
Except that thing was a bug in Safari. They used perfectly valid plain HTML without any hacks or JS.
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.
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.
So you're blaming Google for not writing around an edge case bug that exists only on one platform?