Skip to content

Build: Support jQuery 3.4.1 and use 3.x for grunt test #319

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

Closed
wants to merge 1 commit into from

Conversation

dmethvin
Copy link
Member

@dmethvin dmethvin commented May 9, 2019

Since jquery-git.js already has some 4.x breaking changes we need to avoid using it.

I'm seeing one test failure locally on grunt test related to jQuery.event.props.concat but it's happening on 3.4.0 as well. I don't see any failures on real browsers though.

The most recent Jenkins job failed as well but I don't see anything in the output to explain it: http://jenkins.jquery.com/job/jQuery%20Migrate/412/console

@dmethvin dmethvin requested a review from mgol May 9, 2019 02:11
Copy link
Member

@mgol mgol left a comment

Choose a reason for hiding this comment

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

See the comment.

Jenkins failed because Android timed out. In Core we only make the build “unstable” in such a case, Migrate probably has a hard failure then. You’re not seeing it as I restarted the timed out jobs. ;)

@dmethvin
Copy link
Member Author

dmethvin commented May 9, 2019

Thanks for restarting the jobs!

Copy link
Member

@mgol mgol left a comment

Choose a reason for hiding this comment

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

LGTM now but there's one test failure you might want to look at.

@mgol
Copy link
Member

mgol commented May 10, 2019

It's weird but I can reproduce the issue via Karma (npm test) but not via manually opening the QUnit page, even if I choose the same jQuery + Migrate set.

@dmethvin
Copy link
Member Author

I'm trying to figure this one out. It could occur, for example, if some code outside jQuery or Migrate completely overwrites jQuery.event.props which would wipe out the concat override. What makes it more complicated is that it pulls in jQuery Mobile, specifically because that was the only piece of code that I knew used this hack. I'm not even sure if it makes sense to support jQuery Mobile's nonsense anymore, users can always just use 2.x or something. I do see the message appearing on the console if I run the test standalone though.

@ecadius
Copy link

ecadius commented May 13, 2019

There are also security issues in 2.x https://www.cvedetails.com/vulnerability-list.php?vendor_id=6538
How can we use this version?

@mgol
Copy link
Member

mgol commented May 14, 2019

@ecadius As far as I know, jQuery Mobile itself still doesn't support jQuery 3.0 & later officially, we can't do that work on the jQuery+Migrate side ourselves.

@dmethvin
Copy link
Member Author

I merged this in 4336560 and in the process had to do a bunch of other housekeeping. On Windows the existing deps wouldn't build properly.

@dmethvin dmethvin closed this May 27, 2019
@mgol
Copy link
Member

mgol commented May 27, 2019

On Windows the existing deps wouldn't build properly.

Not only on Windows!

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.

3 participants