cramforce

I don't think it does. Previous versions of Contributor worked in all browsers. It simply doesn't draw an ad for users that. Not really something you need a special browser for :)

When scrolling itself is faster (as is currently the plan for iOS) the gesture is needed less, I assume, since one can just fling up.

Is there a way how the behavior could be implemented in software to match default?

There are no such controls. There are just different places where one can scroll. All other browsers (as far as I know, and this includes Safari on desktop) make all of these the same, but mobile Safari chose to make them different.

That line causes the observed behavior. But it improves it over not being present.

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.

I believe we have a webkit patch pending for this. Definitely on our radar!

Edit: some detail. Safari sometimes doesn't scroll find results into view when they are in overflowed space. This issue actually affects a large percentage of web pages. Fixing it was very easy, was just an oversight in WebKit.

Yeah, I don't care either way. But Safari should have the SAME scroll inertia for every scroll context and ideally it is the same as used for native apps.

Sorry, but there is some irony there. We were as surprised as anyone. I do like the new inertia much better. Allows for much faster scrolling similar to Android.

On top of this: we currently have a team working to fix webkit bugs that are problematic for AMP. This, of course, will make webkit better for everyone.

Big difference was that these had custom renderers. AMP renders in any web browser since they are just web pages.

See comment below. Soon all pages will scroll like AMP. It is just overflow scrolling, and Apple decided to make that the standard.

AMP is HTML5, so by definition it cannot outperform it. It is just the web. That is a feature.

With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling.

Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy then :)

With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling.

Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy then :)

On our radar to get browsers to change and they have been receptive to our proposal.

Only a tiny percentage of users wants to use the "click through to original" feature. Sharing is a major use case that strongly benefits publisher. In the end one has to make trade offs what to make prominent in a UI.

It'll be replaced with a standard share button once navigator.share() API launches.

We added that button to Google Search on the web about a month ago.

The actual answer to the question posed by the blog post is purely technical in nature. Sorry, no conspiracy theory to find here: https://news.ycombinator.com/item?id=13838756

This effect is similar to what is measured when transferring from a WebView (such a Facebook's) to a real browser, since sessions do not transfer. Means the first pageview is considered as a bounce and the second as another unique visitor.

The AMP team is working with analytics vendors to display data as realistic as possible.

At AMPConf on Tuesday eBay gave a great talk how to deal with this phenomenon. Video will be out soon.

The article talks about that in great detail.

Nice derailing of a technical point!

AMP is not a ranking factor and so the percentage of results it makes up is largely a factor of the percentage of publishers publishing AMP.

AMP had 2 multi month public developer previews. Unfortunately it did not come up as a big issue during that phase.

Maybe it doesn't, but it is hard to give somebody who just shoots out rhetorical questions hard data on each one.

I invite you to hangout on the open source project for a while and make your own impression.

8 pull requests for new ad networks were submitted and approved in the last week alone. I'd say the answer to your question is: no.

There is no navigation (only pushState) to enable pre-rendering, so the origin cannot be changed.

We did not invent this. It is the same UI as Chrome Custom Tabs uses for in-app browsers. This may not be familiar on iOS.

Thanks for the feedback! I did, however, announce this change 2 months ago :) https://twitter.com/cramforce/status/794585395056939009

The X tested well with users, but we are reconsidering it, because of the feedback from the developer community!