4 ms·
Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sa
by lloeki 8y ago
Qualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".
- dkersten 8y agoThere’s an “or” in that sentence: “old or unsupported browser”
- giancarlostoro 8y agoThe term unsupported browser sounds like it's intentionally only for Chrome.
- janesconference 8y agoThat's true, that's inaccurate. I'll change the message with the next deploy.
- dkersten 8y agoI’m not saying that the message sounded good, I’m just saying that it’s technically accurate. Other browsers don’t support the bleeding edge features the site needs and therefore they’re unsupported.
- te_chris 8y agoNitpicking cool projects is also pretty disparaging.
- janesconference 8y agoSorry if I hurt any browser's sensibility. Hope no browser was offended by my app :) However, I didn't refer to "browsers that don't follow an early adopter in implementing a working draft" as "old", though; if you read the compatibility message carefully, you'll find I referred to them as "unsupported" (which might be a bit inexact but not disparaging). Non-evergreen browsers, instead, are correctly referred to as "old", because they are.