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.

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

Fix issues with IE11 #276

Merged
merged 3 commits into from
Dec 15, 2017
Merged

Conversation

cibernox
Copy link
Contributor

I think there is still 2 failing tests, but I'm out for the day.

@@ -22,8 +22,8 @@ export default function fillIn(target, text) {
if (!element) {
throw new Error(`Element not found when calling \`fillIn('${target}')\`.`);
}

if (!isFormControl(element) && !element.isContentEditable) {
let isControl = isFormControl(element);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It turns out that isContentEditable is true for input elements in IE. I did this fix but maybe we have to go back to check if the element has a contenteditable=true attribute

@@ -1,5 +1,5 @@
/* eslint-env node */
const browsers = ['last 1 Chrome versions', 'last 1 Firefox versions', 'last 1 Safari versions'];
const browsers = ['ie 11', 'last 1 Chrome versions', 'last 1 Firefox versions', 'last 1 Safari versions'];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably revert this change (to test locally you can use CI=true ember test --server or CI=true ember s -p 0)...

@@ -0,0 +1 @@
export default !window.ActiveXObject && 'ActiveXObject' in window;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! 👍 I think we should add a comment explaining what it does.

Something like:

// `window.ActiveXObject` returns undefined in IE11 (as well as non-IE browsers)
// whereas `"ActiveXObject" in window` returns `true` in all IE versions
// only IE11 will pass _both_ of these conditions

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😨

Fixes linting (to pass CI).
Replace usage of `document.contains` with `document.body.contains` (only
elements get `.contains`).
@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2017

OK, pushed some changes / tweaks to address my comments above.

IE11 PASSING

@cibernox
Copy link
Contributor Author

Now great. Now I need an IE10 vm

@rwjblue rwjblue merged commit 51325db into emberjs:master Dec 15, 2017
@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2017

Great work here @cibernox! Thank you!

@rwjblue rwjblue changed the title Fix almost all tests for ie11 Fix issues with IE11 Dec 15, 2017
@cibernox cibernox deleted the fix-event-ordering-in-ie-tests branch December 15, 2017 21:42
@rwjblue rwjblue mentioned this pull request Dec 15, 2017
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants