wux

Unless I'm mistaken, the same resource shows Chrome 55/56/57 is also at 99%?

I'd be curious if a JavaScript guru could give a little more context about the significance of that last 1%: namely, for Safari, "enumerable properties can be shadowed by non-enumerables," and for Chrome, "Array.prototype.sort: compareFn must be function or undefined."

This looked like a pretty long list of unsupported APIs, so I decided to do some research:

- CSS motion path is not an official standard; it is implemented only in Blink (Chrome/Opera).

- CSS device adaptation is a W3C working draft. It is available prefixed in IE/Edge and Opera Mini, but is unprefixed in 0% of shipping browsers.

- Client Hints: DPR, Width, Viewport-Width is an IETF working draft implemented only in Blink (Chrome/Opera).

- inputmode is supported in 0% of shipping browsers.

- MediaRecorder API is a W3C working draft supported in Blink (Chrome/Opera) and Firefox but not IE/Edge or Safari.

- Network Information API is not an official standard; it is supported only in Chrome for Android.

(Source: caniuse.com)

I stopped going through the list at this point. At least from the top of your list, none of these features are "shipped in every other browser" and some are shipped in no browsers at all. I'm not sure how it shows that Safari is "far behind the times."

If anything, the list seems to show that Chrome implements many non-standard APIs not available elsewhere. Combined with its mindshare (if not marketshare), this suggests that Chrome--not Safari--is in some ways the new IE6.

Unfortunately, you're simply not correct. The fraction of income received by the top 1% of Canadians did not decrease from 2012 to 2013, nor did it decrease from 2010 to 2011.

Source: Statistics Canada http://www5.statcan.gc.ca/cansim/a26?lang=eng&retrLang=eng&i...