You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are going to test browser compatibility, test on availability of required features, not useragent string. All required Web APIs should be checked in utils instead of the browser. Technically it would be possible to run an outdated version of Chrome, although it requires some work, which could render the site useless.
The site works fine in Firefox (only tested in version 97), but requires altering the userAgent string to get past the browser compatibility test.
Are there specific features you require that are not available in other browsers? I understand you might be interested in blocking IE, but Safari is likely to be compatible as well as FF. There are Chromium (Google specific) Web APIs that other browser engines haven't implemented, but unless they are strictly necessary, I don't see why you should be blocking FF and Safari.
Alternatively, you can warn the user that the application might not work correctly in other browsers, and you recommend using Chrome, but allow the user to override anyway. Similar to allowing running unsigned applications on most modern OSes.
The text was updated successfully, but these errors were encountered:
Just to give some more info here, I've been using Firefox Desktop and Safari on iPadOS for a few months via user agent spoofing, and I haven't ran into a single issue.
If you are going to test browser compatibility, test on availability of required features, not useragent string. All required Web APIs should be checked in utils instead of the browser. Technically it would be possible to run an outdated version of Chrome, although it requires some work, which could render the site useless.
The site works fine in Firefox (only tested in version 97), but requires altering the userAgent string to get past the browser compatibility test.
Are there specific features you require that are not available in other browsers? I understand you might be interested in blocking IE, but Safari is likely to be compatible as well as FF. There are Chromium (Google specific) Web APIs that other browser engines haven't implemented, but unless they are strictly necessary, I don't see why you should be blocking FF and Safari.
Alternatively, you can warn the user that the application might not work correctly in other browsers, and you recommend using Chrome, but allow the user to override anyway. Similar to allowing running unsigned applications on most modern OSes.
The text was updated successfully, but these errors were encountered: