[META] Unsupported jQuery libraries: forks, compatibility layers, remove deprecations

[herbdool]

A question was raised on whether we want to add compatibility layers for unmaintained jquery libraries (some of this has already happened for security reasons mostly), or fork them and put them into a separate org. In truth we'll probably be doing both plus remove deprecations where possible.

1. jquery.color.js - https://github.com/jquery/jquery-color - NOT maintained - required by jquery.ui effects
2. jquery.cookie.js - JS: Replace jQuery.cookie with JS-cookie and provide a BC layer #4349 - NOT maintained - usage in core has been effectively removed, though contrib still uses it. Can be replaced by js-color.
3. jquery.form.js - https://github.com/jquery-form/form - NOT maintained; Drupal forked.
4. jquery.once.js - http://github.com/robloach/jquery-once actively maintained
5. jquery.timeentry.js - Update the jQuery Time Entry plugin #6249 - NOT maintained - fork or remove usage?
6. jquery.treetable.js - https://github.com/ludo/jquery-treetable - NOT maintained
7. jquery.ui - https://jqueryui.com - actively maintained
8. jquery.ui.touch-punch.js - https://github.com/RWAP/jquery-ui-touch-punch - actively maintained

Related:

• deprecated jqueryui dialogClass property: dialogClass deprecated in jQuery UI, core usages need to be updated #6184

[indigoxela]

Note that core/modules/system/js/jquery.treetable.js, isn't under "misc" like the other libraries.

Note re jquery.once.js That lib is maintained but in a breaking way we can not use, hence we forked it already by Issue #6195 The comment in that JS file mentions that.

Note re jquery.color.js Not our problem, as that lib ships with jQuery.ui (I was asked to pull it out of the ui directory when updating in Issue #5401. Was in ui/vendor/jquery-color/.)

And there's also smartmenus - not clear whether that one's still maintained.
But we're waaaay behind - probably because of the modifications for Backdrop, which makes updating tricky.

[indigoxela]

For completeness a list of libs provided by core, which we have to update to get compatible with jQuery4:

• core/misc/jquery.form.js
• core/misc/jquery.timeentry.js
• core/modules/system/js/jquery.treetable.js
• core/misc/jquery.cookie.js (not even used in core, only there for bc reasons)

It's still unclear, where we fork and how to handle that.

I'm not convinced, an extra orga with repos is ideal, but it seems feasible.
For a tiny script like jquery.once this seems too complicated and inefficient (we already forked it, anyway).
For a larger libs a repo might make sense... eventually.

What we'd have to define is, how the release process in such an orga should work - which uglify params to use, file comment conventions, how those libs are supposed to get distributed (OK, copied over to core). How maintenance is organized, if in an extra orga... Who's responsible to invite, add perms, revoke...