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
So here's a fun one for you... so you know how you guys are parsing the user agent string to determine whether or not a browser is IE8? The problem is that -- on _INTRA_net sites, as in on an internal network -- IE8 by default goes into Compatibility Mode. Which means its user string actually looks like this:
Meaning the user string check fails -- meaning the code generates a whole bunch of errors afterwards, since the script doesn't know it's running in IE8. I would suggest either relying on feature detection for this, or otherwise (for a quick fix) update line 408 (or thereabouts) in lib.js from this:
var IS_IE8 = (/MSIE\s8\.0/).test(USER_AGENT);
to this:
var IS_IE8 = (/MSIE\s(7|8)\.0/).test(USER_AGENT);
If only to spare some poor idiot out there the same path I've been dealing with all afternoon here.
The text was updated successfully, but these errors were encountered:
Updating the title to "Unsupported Browser" modal.
gkatsev
changed the title
Very specific IE8 Edge Case: Script errors will occur on intranet sites
Add an "Unsupported Browser" modal dialog for unsupported browsers
Mar 28, 2016
So here's a fun one for you... so you know how you guys are parsing the user agent string to determine whether or not a browser is IE8? The problem is that -- on _INTRA_net sites, as in on an internal network -- IE8 by default goes into Compatibility Mode. Which means its user string actually looks like this:
Meaning the user string check fails -- meaning the code generates a whole bunch of errors afterwards, since the script doesn't know it's running in IE8. I would suggest either relying on feature detection for this, or otherwise (for a quick fix) update line 408 (or thereabouts) in lib.js from this:
to this:
If only to spare some poor idiot out there the same path I've been dealing with all afternoon here.
The text was updated successfully, but these errors were encountered: