The problem is the OS zooming fights against pinch zooming that you may implement inside your webapp's logic, especially for non-static content (maps for example), multi-finger games where two touches don't signify a zoom, etc. They just broke the UX of a whole bunch of websites.

When will we ever have HTML5 apps that match native apps? When they actually let HTML5 apps do what native apps do, like multitouch without triggering a default action.

No, that's not the problem. Remember, developers are a minority, users are the majority, so making things work well for users takes priority over making things work well for developers. When functionality that's useful for webapps is misused for websites where it has no place and where it breaks the user experience, the only way to improve things for users is to make things harder for developers.

developers make the things the majority use, if you make things worse for developers they have a harder time making things that work well for the user, when that happens they will look to misuse functionality to improve things for their users. The only way to improve things for users is to make things easier for developers.

There are good developers who try to improve things for their users. There are also many developers who don't and ruin it for the rest.

Do they earn 30% from HTML5 apps?

The OS or browser should not just take over one of the primary means of interacting with an app and effectively disable it for any other use. You might as well just pull those gestures out of the specs at that point. The point of an os or browser is to get out of the way, not be omnipresent. It's extremely patronizing and cripples important functionality for likely millions of sites.

The browser is the app.

The web app is the app. A browser is a mini OS at this point.

That's what web devs like to pretend. Then they are surprised when browser developers continue developing their browsers.

If you want to develop an app, develop an app, not a website. Use Electron or its mobile equivalents if you must.

So you are saying that pinch and double tap should just be removed from js specs because one company arbitrarily decided you can't use them anymore. Whatever.

Also, MS office and Adobe are web apps and far more complex than almost any "real apps" out there. It's completely untrue that web apps are not apps.

No, I think JS as a whole should be removed completely independently of what any company decided. Websites in general aren't trustworthy, which means they can't be trusted to determine the browser's behaviour.

> Also, MS office and Adobe are web apps and far more complex than almost any "real apps" out there. It's completely untrue that web apps are not apps.

You can pretend they are until someone takes away your toys. Then, suddenly, your "app" cannot even process its own input. Or access the clipboard. Or do any of the other things that websites just aren't trustworthy enough for.

There is nothing that makes an installed app, with higher permissions, more trustworthy than a web app. Getting rid of js altogether is just throwing away the web to make it something poorly performing and requires sending all data back to the server - so not really a serious option. Browsers only exist to allow interaction with websites, and as such they should follow specs and allow them to be used. Websites are more important than browsers by definition.

> There is nothing that makes an installed app, with higher permissions, more trustworthy than a web app.

Yes, there is. The fact the user has installed it.

> Getting rid of js altogether is just throwing away the web to make it something poorly performing and requires sending all data back to the server - so not really a serious option.

Not the web, just webapps. The web will perform better afterwards.

> Browsers only exist to allow interaction with websites, and as such they should follow specs and allow them to be used.

Yes, but those specs have to be sane. Which means even a completely untrusted party – that's what a random website is – cannot abuse them.

> Websites are more important than browsers by definition.

Nonsense, either is useless without the other. Websites are content, browsers define how they're viewed.

At what point do they think my English "makes the iOS user experience worse" and change the text between two <div>s?