[Isomorphic]

As we mentioned, we cannot reproduce this issue with any DOCTYPE - quirks, HTML5, or the transitional DOCTYPE you posted either.

It also doesn't matter if IE arrived at HTML5 DOCTYPE indirectly via a meta tag. Our approach for browser mode sniffing doesn't care.

So again you are probably chasing the wrong symptom by focusing on what mode the page is in - it doesn't matter either way. If you're unsure of this, you can quickly verify that DOCTYPE as such, no matter how it's set, is not an issue for SmartGWT by testing outside of your Struts app.

Also FYI, the parent page and iframe can have different document modes. If you've just been looking at the F12 tools, you've only been looking at the mode of the parent frame.

At that point we would recommend looking through the list of basic assumptions to check (our previous post).

[tamt]

Just to clarify where we are on the thread. I found a workaround to the issue by adding the Microsoft custom tag:

<meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" />

to my SmartGWT application. I just want your assessment if this tag is going to break anything in the SmartGWT framework. If there are no issues, I'm going to production with this.

[Isomorphic]

It also doesn't matter if IE arrived at HTML5 DOCTYPE indirectly via a meta tag. Our approach for browser mode sniffing doesn't care.

So, taken in isolation, this approach is fine.

But we have no idea why you're getting the results you are, so we can't really say with confidence that anything in particular is going to work normally in your environment :)

[tamt]

Sounds good. Let's close this issue for now. We are going to get the application through formal verification testing soon so we should know pretty fast if the workaround holds.