-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Update jQuery to v3.5.1. #1362
Update jQuery to v3.5.1. #1362
Conversation
I added a TODO in the OP. From my tests, this has a clear positive effect on load. We should definitely do it after we test the TODO. 🙂 |
ea6d166
to
8694e41
Compare
I'm going to split some of the patches that can land on develop later so that this branch is only left with the jQuery 3.x update. |
1db8d81
to
9d5ec02
Compare
I'm gonna take a stab at fixing the TODO so that we can test this further, tops until tomorrow. I'm not sure if we want to land this in v5.1.0, but the difference is pretty big IMO. |
568d517
to
0c28568
Compare
Not sure what I'm looking for to test here, any pointers welcome |
Should be OK, I meant bootstrap-select. But all of the plugins are up to date so they should be fine. The only plugin that's old is jquery-confirm. So if that works too, we should be fine. EDIT: for what is worth that's one of the reasons I have it in my TODO (#1352) to remove jquery-confirm and use Bootstrap's alerts. But if it still works, it's not something we need to do for 5.1.0. |
Signed-off-by: XhmikosR <xhmikosr@gmail.com>
Signed-off-by: XhmikosR <xhmikosr@gmail.com>
Signed-off-by: XhmikosR <xhmikosr@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on all pages, no unexpected errors in console log. Not sure if further testing is required...
We should be OK hopefully. Unless I missed another breaking change, but hey, mistakes can happen and we can fix them if reported. |
I mean the 3.x BC are a lot, so I tried to check every one of them in our code: https://jquery.com/upgrade-guide/3.0/ The plugins are all updated, so that's something too. |
I already mentioned this somewhere else, but I don't think it's related to this change. Either way, please open new issues and don't comment on old ones because it's hard to track stuff. |
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/pi-hole-5-1-released/35577/1 |
Signed-off-by: XhmikosR xhmikosr@gmail.com
By submitting this pull request, I confirm the following:
{please fill any appropriate checkboxes, e.g: [X]}
{Please ensure that your pull request is for the 'devel' branch!}
git rebase
)git commit --signoff
)I tested it as much as I could and it seems to work OK. Things that could break are one of the jQuery plugins, so we should test them out as good as possible.
It's not urgent to update, but we should try to do it ASAP. There have been several bugxifes, security fixes and plenty of performance improvements.
Browser support should be what we currently support, and I doubt anyone sane would use IE < 9 😛: https://jquery.com/upgrade-guide/3.0/#browser-support
I'm going to go through each of the breaking changes and see if we have code that's using that.
https://jquery.com/upgrade-guide/3.0/
This would leave us 3rd-party code only.
TODO:
.context()
instances in our codeFixes #1014