3 ms·

I'm currently building a website that uses Vue 3 in parts, as well as other features that don't work (well) in IE11 such as CSS Grid. Would you recommend only

by pansa2 5y ago

I'm currently building a website that uses Vue 3 in parts, as well as other features that don't work (well) in IE11 such as CSS Grid. Would you recommend only displaying an error screen for any users who try to view the site using Internet Explorer or another old browser? Or should I let those browsers try to display what they can, and maybe also a warning message?

InfiniteRand 5y ago
My two cents is it depends on the nature of the lack of functionality, is this just about not displaying information or is this going to cause data corruption (ie, if validation checks or expected ajax calls are not being made), if it's just the display of things I would probably go with a warning message.
- pansa2 5y ago
  > if it's just the display of things I would probably go with a warning message Thanks, that's what I was thinking. Is there a standard way to detect whether to show the warning message based on which browser is being used?
  - seumars 5y ago
    There are lot of snippets out there, the most common way would be to target the window.navigator.userAgent, something like: function isIE() { return /Trident\/|MSIE/.test(window.navigator.userAgent); }
    - unilynx 5y ago
      Keep in mind that the code has to compile for checks to work. Eg a ‘let’ in the same script block will break the isIE check too and it’s easy to miss that someone broke it. How often does the ie11 code get tested on ie11.. Best to keep the IE 11 warning code in a separate (nomodule?) script file
The_rationalist 5y ago
Redirect them to https://browser-update.org/update.html?force_outdated=true https://browser-update.org/update.html?force_outdated=true
seumars 5y ago
As a general rule you shouldn't bother with IE11 at all unless the project explicitly requires it.
- pansa2 5y ago
  Do you mean I should just ignore it? Not even display a warning message?
  - dbbk 5y ago
    Why would you waste your time? Life is too short. Someone using IE 11 at this point is well aware that many things are destined to break.
babypuncher 5y ago
My B2B app is completely broken in IE. I just let it stay that way. No warnings. Tech support knows to tell customers to use Firefox, Chrome, or Safari if they run into issues. It's such a rare occurrence that it is not worth the effort to detect an ancient browser and render a warning.

by pansa2 5y ago

InfiniteRand 5y ago

My two cents is it depends on the nature of the lack of functionality, is this just about not displaying information or is this going to cause data corruption (ie, if validation checks or expected ajax calls are not being made), if it's just the display of things I would probably go with a warning message.

pansa2 5y ago
> if it's just the display of things I would probably go with a warning message Thanks, that's what I was thinking. Is there a standard way to detect whether to show the warning message based on which browser is being used?
- seumars 5y ago
  There are lot of snippets out there, the most common way would be to target the window.navigator.userAgent, something like: function isIE() { return /Trident\/|MSIE/.test(window.navigator.userAgent); }
  - unilynx 5y ago
    Keep in mind that the code has to compile for checks to work. Eg a ‘let’ in the same script block will break the isIE check too and it’s easy to miss that someone broke it. How often does the ie11 code get tested on ie11.. Best to keep the IE 11 warning code in a separate (nomodule?) script file

The_rationalist 5y ago

Redirect them to https://browser-update.org/update.html?force_outdated=true https://browser-update.org/update.html?force_outdated=true

seumars 5y ago

As a general rule you shouldn't bother with IE11 at all unless the project explicitly requires it.

pansa2 5y ago
Do you mean I should just ignore it? Not even display a warning message?
- dbbk 5y ago
  Why would you waste your time? Life is too short. Someone using IE 11 at this point is well aware that many things are destined to break.

babypuncher 5y ago

My B2B app is completely broken in IE. I just let it stay that way. No warnings. Tech support knows to tell customers to use Firefox, Chrome, or Safari if they run into issues. It's such a rare occurrence that it is not worth the effort to detect an ancient browser and render a warning.