Replace jQuery UI in CP back-end: First Step: Draggable, Droppable, Sortable about classicpress-v2 HOT 2 OPEN

I like the idea. My main question is, what happens if a plugin/theme enqueues those scripts? Will we continue to include them for backward compatibility?

HTML5Sortable disclaimer says:

A fair warning: this repository is currently not being actively developed. It works pretty fine, but if you find any issues you will need to fix them yourself. I try to keep the dependencies up to date and will happily help you fix issues and merge PRs for bugfixes or new features.

So if we find issues, we could submit PRs or fix our own copy of the library.

from classicpress-v2.

I like the idea. My main question is, what happens if a plugin/theme enqueues those scripts? Will we continue to include them for backward compatibility?

Initially, we'll keep the scripts in the CP bundle, so anyone using them in a theme or plugin wouldn't be affected. (This will, of course, mean that we increase the download size of CP a little as we add the new libraries, but we won't be loading the old scripts.)

If and when we get well along in this project, then I'd suggest we add a deprecation warning whenever someone uses jQuery UI, so that we could remove it altogether from the CP bundle the next time we release a major version. But it will take some time before we get there, and we could even write some blog posts on how (and with what) we've replaced jQuery UI modules, so that those currently using them would have a model on how to follow suit.

So if we find issues, we could submit PRs or fix our own copy of the library.

Yes, that's what I'm thinking too.

from classicpress-v2.