it seems that it is not clear what is better - forcing IE11 to behave like IE10 or letting it behave like gecko (Firefox) - there are arguments for both sides.
I am closing this; need to re-open if problems occur in 3.3 and:
- only on IE11 (IE10-, other browsers should be fine)
- those problems don't occur in 3.4+.
[1] https://code.google.com/p/google-web-toolkit/issues/detail?id=8228
I quickly went throught GWT issue #8228 mentioned by Einav in comment #3.
"
To reiterate; we will not introduce a new permutation until we discover too many customizations required for IE11 and if it happens that permutation will very likely fallback to 'gecko' not 'ie10'.
"
Microsoft claims that IE11 is very close to FF, which is also why they changed IE11's user agent string to contain "like Gecko". As I understand it, for now, GWT team is NOT planning to introduce separate IE11 permutation. (And if they do that in future, IE11 permutation will fall back to FF permutation and NOT to IE10 permutation.)
So I agree that for now, the best solution is to close this issue - IE11 should simply work with FF permutation of GWT application.