WordPress.org

Make WordPress Core

Opened 3 years ago

Last modified 3 years ago

#37675 new enhancement

Update Masonry (v4.1.0) & imagesLoaded (v4.1.0) package

Reported by: grapplerulrich Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.6
Component: External Libraries Keywords:
Focuses: javascript Cc:
PR Number:

Description

As this updates drops IE8 and 9 support we cannot update directly to these versions. We can't make the same switch from jquery-masonry to masonry as we don't have a shiv and which is a bit counterproductive if IE 8 & 9 support has been dropped.

I think it would be good to think for the future as I expect version v5 will also be a breaking change.

Possible solutions:

  • Register a new handle masonry-4
  • Deprecate Masonry from core. jquery-masonry is used for the custom-header script, Twenty Thirteen and Twenty Fourteen.
  • Add an option to wp_enqueue_script to define which version of script that is needed. We can include v3.x and v4.x and the developer can define which version that they need.

Masonry

imagesloaded

Change History (1)

#1 @pderksen
3 years ago

+1 the idea of registering new handles such as masonry-4& imagesloaded-4.

We're using imagesLoaded 4.x in Simple Calendar, which is a dependency of qTip2 (also used in the plugin and by the same author).

Should we also have the unminified versions of these libs (old and new versions) included for debugging purposes (and to follow suit with other JS libs)?

Note: See TracTickets for help on using tickets.