My users are getting the following in IE 11 (Discourse version v1.9.0.beta2 +218) on Windows 10: [이미지] I don’t see this on meta or https://try.discourse.org/ in IE 11 on the same browser, so I thought that maybe a plugin is causing the problem. When I enter into safe mode and disable everything, …

Not sure if this is helpful / or you already know, but to disable compatibility mode, go to tools > compatibility mode settings and uncheck the display intranet site in compatibility view setting / or remove the discourse site from the compatibility sites list. [이미지]

[이미지] wesochuck: I don’t see this on meta or https://try.discourse.org/ in IE 11 on the same browser Safe mode does not cover everything – server side effects of plugins still exist.

So the only way to test for server side issues with plugins is to remove them one-by-one in the yml and rebuild? This is what we’re running: discourse-assign discourse-data-explorer discourse-details discourse-narrative-bot discourse-nginx-performance-report discourse-solved Are there any known …

No, those are all official and should not cause problems. It is very weird that you cannot reproduce this on try! There is something different about your instance, somehow.

[이미지] codinghorror: There is something different about your instance, somehow. Any suggestions about how to find that difference :wink: We’re running a docker based install on Ubuntu on a local virtual machine in case that makes any difference. We also are using SSO and require users to have…

Can you get to a JS console on this browser and check the value of window.ie ?

Total JS developer noob here, so please bear with me. I dropped to the IE 11 console and typed alert(window.ie) and got an undefined back. Not sure if that is the proper way to go about getting that information though, so glad to try something else if I’m doing it totally wrong. I did verify earlie…

The script that shows this message is pretty straightforward, so I recommend following it and testing each variable to find why this message is appearing.

I think window.ie doesn’t exist. It was set at one point in an html conditional but was removed: https://github.com/discourse/discourse/commit/e1f90d12f14cd72c5624538dc1ad5732093553ad#diff-9599427925097c3c66f26ac1e0de5cadL63

As Falco said, it’s a simple script, and window.ie doesn’t need to be defined, as long as window.history.pushState is truthy and the UA doesn’t include “Android 2.2” or “Android 2.3”, the warning bar won’t be shown.

Our developer is back in the office later this week, so I’ll see if he can help me step through some of this and we’ll update the thread.

Browser too old message when "compatibility mode" is forced in IE 11

지원

codinghorror (Jeff Atwood) 7월 3, 2017, 7:27오후 2

Safe mode does not cover everything – server side effects of plugins still exist.

글		댓글	조회수
Problems clicking topic links in IE11 Support	9	2711	1월 4, 2019
Site does not work on Internet Explorer 11 after recent update Support	2	806	8월 11, 2019
IE 10: Blank page is showing rather not supported message Bug	5	1118	5월 6, 2019
Infinite loop when mentioning in IE11 Support	5	1113	5월 1, 2020
Discourse is ending support for Internet Explorer 11 (IE11) on June 1, 2020 Announcements	5	8652	6월 14, 2022

Browser too old message when "compatibility mode" is forced in IE 11

Related topics