My users are getting the following in IE 11 (Discourse version v1.9.0.beta2 +218) on Windows 10: [Bild] 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. [Bild]

If window.history.pushState is undefined, there’s your problem – if that’s false, you’ll get told your browser is too old. I’m not an expert on this part of things, but my understanding is that that is something that is provided by the browser (as part of the browser’s support for HTML5), not by Di…

Look at the warning at the top: The attached page targets document mode 7. Some console APIs and features may not be available. Something is making IE run in compatibility mode. Search Stackoverflow, there are some questions that seem relevant.

This might be relevant to Discourse: [Luke Woodward] IE11 window.history.pushState "Object doesn't support property or method 'pushState' javascript, html, internet-explorer-11, history answered by Luke Woodward on 04:57PM - 11 Apr 15 UTC …

[Bild] Hector: Look at the warning at the top: The attached page targets document mode 7. Some console APIs and features may not be available. Good catch. I brushed straight over that. Most of the stuff I can find on that error talk about fixing it by setting X-UA-Compatible (via http-equiv…

[Bild] mpalmer: but as far as I can see meta doesn’t do that, either Meta isn’t on an intranet. Maybe this is the problem: [Bild] wesochuck: We’re running a docker based install on Ubuntu on a local virtual machine in case that makes any difference.

Really great detective work that is almost certainly it; on your local network ie11 is forcing old browser compatibility mode.

We should just add the header back

Nah, I object to serving this header 100% of the time to everyone to fix the .01% of the time this is an issue.

I’m disturbed by the idea that IE11 would assume, prima facie, that anything “local” (same subnet? on any RFC1918 address?) would require compatibility mode.

[Bild] mpalmer: anything “local” (same subnet? on any RFC1918 address?) would require compatibility mode. It is possible that we have it in our Trusted zone to allow users to access the site without having to log into it directly (uses Windows credentials). I’ll have to check when I get back…

Browser-zu-alt-Meldung, wenn "Kompatibilitätsmodus" in IE 11 erzwungen wird

Unterstützung

tgondorf 20. November 2017 um 09:29 31

We have worked around the issue by establishing an additional nginx-instance proxying discourse and adding the appropriate headers to disable compatibility mode.

Thema		Antworten	Aufrufe
Problems clicking topic links in IE11 Support	9	2711	4. Januar 2019
Site does not work on Internet Explorer 11 after recent update Support	2	806	11. August 2019
IE 10: Blank page is showing rather not supported message Bug	5	1118	6. Mai 2019
Infinite loop when mentioning in IE11 Support	5	1113	1. Mai 2020
Discourse is ending support for Internet Explorer 11 (IE11) on June 1, 2020 Announcements	5	8652	14. Juni 2022

Browser-zu-alt-Meldung, wenn "Kompatibilitätsmodus" in IE 11 erzwungen wird

Verwandte Themen