[poiuytrewqa]

Having standards does not imply no more new APIs. But creating them only for one browser doesn't bring progress on the web but rather lead to monopoly and at the end inaccessibility.

Consider that with chrome (and chromium based browser) we're close to the situation we had back in the days with IE.

So I'd say open standard definition for web API should come first, later each browser will have their own release process to include them inside but at least behavior and aspect are defined upfront and this will avoid lots of issue

As of today for example and I'm using both Firefox and Chrome daily. You'd be surprised on how many website have been tested only in Chrome and some stuff do not work in Firefox at all

[byko3y]

>Consider that with chrome (and chromium based browser) we're close to the situation we had back in the days with IE. >So I'd say open standard definition for web API should come first, later each browser will have their own release process to include them inside but at least behavior and aspect are defined upfront and this will avoid lots of issue

Just a sheer complexity of the layers being deposited during the current and the previous century makes it impossible for a single person to understand all the possible interactions. So today's situation with chromium-based browsers differ from IE in that the latter deliberately went against existing standards while creating many non-standard features.

In the last years google set a course for putting more and more features into browser so no other browser can catch up quickly enough. And despite the fact google actually tries to be standard-complaint and to create standards for their new feature, but only a large corporation is able to implement those features e.g. Mozilla.