@backspace wrote:
Hey, I’m looking at updating
travis-web
to Ember 3. Having checked our analytics, I see that there are still a handful of users who visit with older versions of Internet Explorer that are no longer supported in the new major version; over a dozen in the past weekIt’s a business decision whether it’s okay to end support for these browsers, but if we do decide to do so, I’m wondering what approaches people are using to catch unsupported browsers before they run into any exceptions caused by Javascript they can’t handle. I suppose user agent sniffing is the answer, though I’ve accumulated an aversion to that from the old days…?
This isn’t exactly an Ember-specific problem but I wanted to ask here in case anyone had any special approaches
Posts: 4
Participants: 3