3 ms·
It isn't great at all, because even that living standard is never being implemented up to spec, often by the same people who wrote it, and the current browser s
by baybal2 7y ago
It isn't great at all, because even that living standard is never being implemented up to spec, often by the same people who wrote it, and the current browser support status usually ends up being "what's written in bugzilla"
- nicoburns 7y agoThere are very comprehensive browser support matrices at https://kangax.github.io/compat-table/es6/ https://kangax.github.io/compat-table/es6/ (JavaScript features) and https://caniuse.com/ https://caniuse.com/ (DOM features). It's only for very recently implemented features that you should need to look in bugzilla.
- realityking 7y agoJavaScript (EcmaScript) follows a more traditional standard process, though at a very high pace. caniuse.com is amazing but let‘s not kid ourselves what it covers. It‘s about feature availability. Some feature might have 1000s of normative behaviors specifics but their being condensed down to there/not there.
- domenicd 7y agoA better resources is https://wpt.fyi/ https://wpt.fyi/, which contains comprehensive test results in all browser engines. These days, at least for WHATWG specs, tests are required before any changes land in the specification, so wpt.fyi will necessarily contain all browser support for all features landed in the specs.
- kevingadd 7y ago"should", sure, but vendors (I mostly run into this w/Chrome but other vendors do it too) happily just ignore the spec because it's inconvenient and sometimes explicitly have no plans to ever align with it. I recently ran into a case where Chrome was intentionally moving away from the spec without making any effort to update the spec, because being correct was... annoying. Not impossible or bad for users, just annoying. At the time the behavior worked right in Firefox and Edge but now that Chrome is going to ignore the spec I suspect the other vendors might too. (For reference, it was an issue related to the lifetime of javascript objects for frames that have been unloaded or navigated) This sort of thing will never appear in a compatibility matrix. You find out when it breaks your code.