Make WordPress Core

Opened 3 months ago

Closed 10 days ago

#51210 closed feature request (wontfix)

Feature Request: Add isotope by metafizzy for filtering

Reported by: whimsycollective Owned by:
Milestone: Priority: normal
Severity: minor Version:
Component: External Libraries Keywords: 2nd-opinion
Focuses: ui, javascript, css Cc:


Hi dev team,

Thank you for the hard work you put into WP. I'm happy to see there's Masonry in WP.

I wish that isotope.metafizzy.co was included as core in wp-includes/js. Meanwhile, Masonry by David Desandro (cool to have) is in there.

The outcome of this feature request:

  1. Minimize the use of plugins and reduce the external http request and just to name a few cases below
  1. Add filter functionality by default for whatever the use case are needed for category and tags filters, gutenberg blocks filter option, images and galleries filters, jetpack portfolio filtering for category or tag, pages or posts, or CPT portfolio (non-jetpack).
  1. Basically; allow theme developers to add isotope.js to their functions.php via wp_enqueue_script.

Currently; I'm not fond of the available solutions in plugins where they overlap in features and other times the documentation is sparse in how-to use, what does it do, and how can it be used. Also, there's no support for filtering image/gallery blocks in WP (just a thought).

So far, here's an article I've known about in how-to implement it since WP v4 (it makes reference to WordPress 3.2 though).


Any considerations (please 🙏)?

Change History (4)

#1 @johnbillion
3 months ago

  • Component changed from General to Script Loader
  • Focuses accessibility docs administration template multisite performance coding-standards removed
  • Severity changed from major to minor

#2 @whimsycollective
3 months ago

@johnbillion thank you for the correction on the focus attributes to this ticket 👍

#3 @desrosj
3 months ago

  • Component changed from Script Loader to External Libraries
  • Keywords 2nd-opinion close added

Hi @whimsycollective,

Welcome to Trac! Thanks for this suggestion.

Going to provide some brief history on Masonry in WP Core for context. Masonry was introduced into WordPress in [20060] because it was needed for arranging thumbnails on the custom header screen.

Usually, new external libraries are not added to the code base unless there is a need within WordPress for it, or there is significant demand. I'm not sure that I see the use case here based on your description. I'm having a hard time picturing the how the category and tag filtering could work in a theme agnostic manner, and not all themes require filtering. So I'm not sure that is a good feature to add to Core. Also, a portfolio post type is not something supported in WP by default, Jetpack is also maintained externally, and anything block editor related would need to be adjusted through the GitHub repository.

I'm going to suggest this be closed out as a wontfix, but going to also mark for a second opinion. If I am misunderstanding the suggested use case, @whimsycollective please feel free to add more details to clarify.

#4 @desrosj
10 days ago

  • Keywords close removed
  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Since no one has weighed in for several months, I am going to close this out as it does not seem like a good fit for WordPress Core.

Note: See TracTickets for help on using tickets.