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

issue-1303: updated to jquery 3.1.1 #1304

Merged
merged 1 commit into from
Feb 10, 2017
Merged

issue-1303: updated to jquery 3.1.1 #1304

merged 1 commit into from
Feb 10, 2017

Conversation

oliverfoster
Copy link
Member

@brian-learningpool
Copy link
Member

JQuery 3+ doesn't seem to support IE 8.
https://jquery.com/upgrade-guide/3.0/#browser-support

@moloko
Copy link
Contributor

moloko commented Nov 8, 2016

@brian-learningpool jquery v1 is loaded for IE8 - see scriptLoader.js

@brian-learningpool
Copy link
Member

Great, thanks for clarifying.

@oliverfoster
Copy link
Member Author

i thoroughly recommend you test this with all your commonly used plugins and extensions. it may break some of the more outlandish ones.

@brian-learningpool
Copy link
Member

I guess we need a full regression test on a course with the core plugins before this is merged?

@oliverfoster
Copy link
Member Author

I'm not so much worried about the core plugins. It's more 3rd party plugins I'm concerned will break. We need a way to mitigate that. I'm a bit lost in the jQuery migration docs. Perhaps you could have a read and suggest a decent course of action?

@brian-learningpool
Copy link
Member

I will read when I get a chance. Is there a pressing reason to upgrade to JQuery v3 at this moment or could it wait until the next major release of the framework?

@oliverfoster
Copy link
Member Author

It can wait until we're all happy.

@moloko
Copy link
Contributor

moloko commented Nov 10, 2016

@brian-learningpool it's really just to take advantage of v3 (supposedly) being faster than v2

@moloko
Copy link
Contributor

moloko commented Nov 10, 2016

I just used JQuery v3 (and the updated inview) in a build where I was testing some updates made to confidenceSlider. Didn't notice any problems but it wasn't the most exhaustive of tests by any means. Only checked in Firefox for a start.

@moloko
Copy link
Contributor

moloko commented Nov 10, 2016

should we stick a post on the forums asking people to test this (and maybe inview as well)?

@brian-learningpool
Copy link
Member

Hi @moloko, to answer your question (apologies for the delay), I think yes, we we should ask forum users to test this.

@moloko
Copy link
Contributor

moloko commented Jan 9, 2017

@moloko
Copy link
Contributor

moloko commented Jan 30, 2017

no feedback from forum users; agreed with @brian-learningpool to put this on hold until 02/02/17

@moloko moloko merged commit 401a250 into master Feb 10, 2017
@moloko moloko deleted the issue-1303 branch February 10, 2017 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants