Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support IE11 through IE9 compatibility mode #4483

Closed
vaadin-bot opened this issue Sep 24, 2013 · 5 comments
Closed

Support IE11 through IE9 compatibility mode #4483

vaadin-bot opened this issue Sep 24, 2013 · 5 comments

Comments

@vaadin-bot
Copy link
Collaborator

Originally by @johndevs

Vaadin 6.8 should force IE 11 into IE9 mode using X-UA-Compatibility=IE9. Native IE11 support will be in Vaadin 7.2 (#12629)
@vaadin-bot
Copy link
Collaborator Author

Originally by @johndevs

Currently IE10 support is implemented in Vaadin 6 by falling back to IE9 mode. IE11 should do the same.

@vaadin-bot
Copy link
Collaborator Author

Originally by @johndevs

Reviewed by Leif Åstrand.

@faenschi
Copy link

Hi all

i have some problems with IE11. When i start our Vaadin 6.8.17 Application locally in JBoss EAP 6.4 everything works fine. The generated css looks good:
<body class="v-generated-body v-ie v-ie9 v-ie90 v-trident v-win" scroll="auto">

When I login into the same Application running on our Testsystem (Windows 2012 & JBoss EAP 6.4) the generated css looks different
<BODY class="v-generated-body v-ie v-ie7 v-ie70 v-trident v-win" scroll=auto>
And with this css some Buttons will not be rendered.

Both times i use the same IE11. Does anybody have an idea?

regards
Angela

@hesara
Copy link
Contributor

hesara commented Aug 23, 2017

Unfortunately Vaadin 6 has reached its support EOL, so the development team will not spend time investigating such issues. My first guess would be that the IE is started with different profiles/compatibility settings (or uses different settings for different servers) depending on whether it is run by the test system or manually. Alternatively, there could be something wrong in the browser version detection code.

You could also try the forum, or ask the Vaadin sales team about the possibility of paid support for a version past its EOL. Otherwise, the debugger and the source code (included in the JAR for Vaadin 6) are probably your best friends here.

@faenschi
Copy link

@hesara thanks for the answer. i already wrote a patch/workaround for this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hesara @faenschi @vaadin-bot