[MGNLUI-3249] Magnolia doesn't work on IE 10 and IE 11 Created: 10/Nov/14  Updated: 17/Mar/17  Resolved: 23/Feb/15

Status: Closed
Project: Magnolia UI
Component/s: admincentral
Affects Version/s: 5.3.5
Fix Version/s: 5.2.12, 5.3.8

Type: Bug Priority: Critical
Reporter: Sebastian Knebel Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: ie
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-3359 Make sure Magnolia 5.4 runs on Edge m... Closed
Relates
relates to MGNLUI-3846 Edit bars and actions are missing in ... Closed
relation
is related to MGNLUI-3329 Vaadin requests are not sent in time ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It is not possible to edit pages in Magnolia using IE10 and IE11. -There was a bug fix in Magnolia 5.2 but in 5.3.5 it does not work.- The problem is, that the green bars do not occur and the action bar is empty.

As pointed out in the comments, Vaadin 7.1 does not support IE11 very well, and switching to IE9 compatibility mode seems to fix this issue. We should override Vaadin's default X-UA-Compatibility tag accordingly, in the BootstrapHandler.

Also mind that this is not relevant for 5.4.



 Comments   
Comment by Thomas Duffey [ 06/Feb/15 ]

Any update on this issue? We're experiencing it on Windows 8 IE 10 and 11.

Comment by Mikaël Geljić [ 06/Feb/15 ]

Hi Sebastian, Thomas,

As far as we could see, Magnolia 5.2 and 5.3 work equally fine on IE10/IE11.
Maybe you are using IE's compatibility mode? — it basically simulates IE7, which isn't even supported by Vaadin 7, for what it's worth.

Can you make sure this policy is turned off for your magnolia domain?

For more information please take a look at Microsoft's official statement: https://msdn.microsoft.com/en-us/library/dn321449.aspx

Today however, more standards-based websites are broken by attempting to appear like they did in Internet Explorer 7.

Do let us know if you still encounter this issue.

Cheers,
Mika

Comment by Ryan Breuer [ 06/Feb/15 ]

Hi Mikaël,

We were able to replicate the issue on the magnolia demo site using Windows 8 and IE11: http://i.imgur.com/kST1gaM.png
It seems to work until you get to editing a page. Here's the page we tried editing in the screenshot above: http://demo.magnolia-cms.com/.magnolia/admincentral#app:pages:detail;/demo-project/about/history:edit

Based on the developer tools, it it switching to IE10 mode: https://i.imgur.com/vkinbbM.png When I tried switching the document mode to IE11 (Edge), I get a couple JS errors (http://i.imgur.com/rT4ocAg.png) and it sits on the loading bar. We are seeing the same issues on our instances.

Let me know if you need any more information.

Comment by Mikaël Geljić [ 10/Feb/15 ]

Hi,

I have a Windows 8.1 VM with IE11, and unfortunately I was unable to reproduce the issue, I do get the green bars here .
I'll get my hands on a real Windows machine to compare. Maybe you can be more specific about what hardware you use too, might help us reproduce.

That said, switching to IE10 mode is expected, it's actually the only supported way in the Vaadin 7.1 series. See http://dev.vaadin.com/ticket/13102 for more info.
We use Vaadin 7.1.7 in both Magnolia 5.2 and 5.3, so for the sake of completeness, there is no difference in IE support between 5.2 and 5.3 — unlike stated in ticket description.

Cheers,
Mika

Comment by Ryan Breuer [ 11/Feb/15 ]

Found out that we have one machine where IE11 is working. It is running an older version of IE11 though. I've also seen it working on browserstack with older versions of IE11. I'm going to try updating the one machine here that is working and see if it still works with the latest updates and then get back to you with more information.

Here's the versions that we've tested:
Windows 8.1
IE 11 Version 11.0.9600.17631 (Update versions: 11.0.16) - not working
IE 11 Version 11.0.9600.17498 (Update versions: 11.0.15) - not working
IE 11 Version 11.0.9600.17031 (Update versions: 11.0.7) - working
IE 11 Version 11.0.9600.16663 (Update versions: 11.0.8)(Browserstack) - working

Comment by Ryan Breuer [ 11/Feb/15 ]

Updated the machine that is working here and it is still working on the latest IE11 update: (17631, update version 11.0.16)

Here's the dxdiag specs on the working machine: https://www.dropbox.com/s/bcfytf3fjztmwkj/Vaio-DxDiag.txt?dl=0

and the non-working machines:
https://www.dropbox.com/s/h4utgf30itj66bq/Lenovo-DxDiag.txt?dl=0
https://www.dropbox.com/s/25h710pz9e4gay6/DxDiag.txt?dl=0
https://www.dropbox.com/s/om2th7zv2vb67an/TVDxDiag.txt?dl=0

Let me know if there's any other information that would be helpful in diagnosing the issue.

Comment by Mikaël Geljić [ 12/Feb/15 ]

Thanks Ryan for the feedback, that's greatly appreciated.

Here I could give it a go on Windows 7/IE11 (haven't checked the exact version though).
I had slightly different issues w/ click handlers at first. But whenever I was browsing "InPrivate" everything was fine, including page-editor. Same goes when I was switching to IE9 mode.

Do you mind trying the IE9 mode on those machines as well? — I found out it's also the X-UA-Compatibility default for the Vaadin 6 branch, for what it's worth.
If it works, we could probably make it the default compatibility tag on our side — at least until Magnolia 5.4, where things should get back in order for the Edge mode with the Vaadin upgrade. Unfortunately, we normally avoid library upgrades for bugfix releases.

Cheers,
Mika

Comment by Ryan Breuer [ 12/Feb/15 ]

Switching to IE9 mode does work.

Comment by Mikaël Geljić [ 13/Feb/15 ]

That's "great" news! We'll schedule this as soon as possible then.
Thanks again for your input and your time

Generated at Mon Feb 12 09:04:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.