#61835 closed defect (bug) (fixed)
Update jQuery Color library
Reported by: | desrosj | Owned by: | desrosj |
---|---|---|---|
Milestone: | 6.7 | Priority: | normal |
Severity: | normal | Version: | |
Component: | External Libraries | Keywords: | good-first-bug has-patch needs-testing |
Focuses: | Cc: |
Description
Version 3.0.0 is now available.
The full list of changes since the last update in Core can be found on GitHub: https://github.com/jquery/jquery-color/compare/3.0.0...2.2.0.
This update notably makes changes to the library's browser and jQuery support policies and should be tested/examined closely.
- Drop support browsers other than the latest Chrome, Firefox, Safari, and Edge
- Drop support for jQuery <1.12 & <2.2
Attachments (3)
Change History (10)
#2
@
4 weeks ago
Sorry, I just noticed that I accidentally added the same patch three times. All the files are identical, so any of them can be reviewed.
#3
@
4 weeks ago
- Keywords has-patch needs-testing added; needs-patch removed
Thanks @vipulgupta003! Could you also open a pull request on GitHub? This will run the entire test suite and confirm that there are no unanticipated side effects of updating this.
If you're unsure how to do this, you'll find details on the related page within the Core handbook.
This ticket was mentioned in PR #7168 on WordPress/wordpress-develop by @vipulgupta003.
4 weeks ago
#4
#6
@
8 days ago
- Owner set to desrosj
- Resolution set to fixed
- Status changed from new to closed
In 58956:
Dove into the history of jQuery versions. Core last shipped 1.12.x in 5.5, entirely skipping 2.x and going right to 3.3.1 for WP 5.6 in [49101] (see #50564). Since it's been over 4 years since a version of jQuery relevant to this change has shipped in Core, this update should not be a problem from that perspective.
For the change in browser support policy, Core's current policy as documented in the handbook is:
The jQuery Color README file says: "Other browsers may also work correctly with this plugin but support is not guaranteed." This seems reasonably similar to Core's policy. The
current-1
version should not differ enough for this to be a problem.