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

Stop using addEventListener/removeEventListener for IE8 compatibility #183

Closed
wants to merge 7 commits into from

Conversation

StefanBilliet
Copy link

Hi

As discussed in issue 175, here is the pull request.
npm test, npm run lint and npm run style all pass, so I hope everything is in order.

With kind regards
Stefan Billiet

@StefanBilliet StefanBilliet changed the title #175 issue #175 May 12, 2015
@dcousens
Copy link
Collaborator

Please squash to 1 commit.

@dcousens dcousens changed the title issue #175 Stop using addEventListener/removeEventListener for IE8 compatibility May 18, 2015
@@ -37,7 +37,9 @@
<div class="footer">
Copyright &copy; Jed Watson 2014. MIT Licensed.
</div>
</div>
</div>
<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/es5-shim/4.1.1/es5-shim.js"></script>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are these necessary?

Copy link
Author

Choose a reason for hiding this comment

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

Without the shim, the example wouldn't run under IE8, so I couldn't verify wether the fix worked.

Copy link
Collaborator

Choose a reason for hiding this comment

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

If we were going to use a shim, why not just use what we had before?

Copy link
Author

Choose a reason for hiding this comment

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

because the shim doesn't abstract away the difference in api of attaching an event handler between IE8 and all other browsers

@StefanBilliet StefanBilliet deleted the issue175 branch May 18, 2015 07:16
@dcousens
Copy link
Collaborator

@StefanBilliet whats the conclusion?

@StefanBilliet
Copy link
Author

That I was doing something very stupid with my branches; trying to rectify the situation -_-

@StefanBilliet
Copy link
Author

I created a new PR here: #193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants