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

Make Matomo more compatible with jQuery 3 #16187

Merged
merged 1 commit into from Jul 7, 2020
Merged

Make Matomo more compatible with jQuery 3 #16187

merged 1 commit into from Jul 7, 2020

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented Jul 7, 2020

refs matomo-org/matomo-for-wordpress#314

Tested Matomo for WordPress with jQuery 3 but nothing was shown until I made these two changes. I added jQuery migrate to find this problem. JQuery migrate complained about this:

"HTML tags must be properly nested and closed: <div class="reporting-page">

    <div piwik-activity-indicator loading="loading"/>

    <div ng-show="hasNoPage">{{ 'CoreHome_NoSuchPage'|translate }}</div>

Once I made these two changes, Matomo seems to work nicely with jQuery 1, jQuery 2 and jQuery 3.

Whether we upgrade to jQuery 3, while still using jQuery 1 in Matomo for WordPress is still to be seen. I didn't do a full test so can't guarantee that everything works with jQuery 1 and 3 but it's a step in the right direction.

@tsteur tsteur added not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. Needs Review PRs that need a code review labels Jul 7, 2020
@tsteur tsteur added this to the 4.0.0 milestone Jul 7, 2020
@tsteur tsteur merged commit 3a29486 into 4.x-dev Jul 7, 2020
@tsteur tsteur deleted the jquery3 branch July 7, 2020 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants