Update to jquery UI 1.14.0 beta

Created on 15 May 2024, about 1 month ago
Updated 22 May 2024, about 1 month ago

Problem/Motivation

https://blog.jqueryui.com/2024/05/jquery-ui-1-14-0-beta-1-released/

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Downport

Version

10.4 ✨

Component
BaseΒ  β†’

Last updated about 2 hours ago

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

Live updates comments and jobs are added and updated live.
  • Needs frontend framework manager review

    Used to alert the fron-tend framework manager core committer(s) that a front-end focused issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

  • Needs release manager review

    It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @larowlan
  • Merge request !8093Update jquery UI to beta 14 β†’ (Open) created by larowlan
  • Status changed to Needs review about 1 month ago
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10
  • Status changed to RTBC about 1 month ago
  • πŸ‡³πŸ‡ΏNew Zealand quietone New Zealand

    Took a minute before I remembered how to update jquery but I got there. I did this locally and the resulting changes matche the changes in the MR. And it applies to 110.0.x as well.

  • πŸ‡³πŸ‡ΏNew Zealand quietone New Zealand
    • alexpott β†’ committed 55c348aa on 11.0.x
      Issue #3447472 by larowlan, quietone: Update to jquery UI 1.14.0 beta
      
      (...
  • Status changed to Fixed about 1 month ago
  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    Committed and pushed 539c50a257 to 11.x and 55c348aaaf to 11.0.x. Thanks!

    I can confirm that the build does not result in any changed files.

  • πŸ‡¬πŸ‡§United Kingdom catch

    Do we want to consider backporting this to 10.4? It looks like if we re-enable compat mode, it might be a small enough change that this would be reasonable to do, but I didn't look into enough to be confident yet.

  • πŸ‡΅πŸ‡±Poland m_gol

    If you can, definitely consider backporting this! The full changelog for the beta is https://jqueryui.com/changelog/1.14.0-beta.1/. Most breaking changes are dropping support for some older browser / jQuery releases, the back compat flag can be reversed. Beyond that, changes are pretty minor, even the included jQuery Color major update is pretty minor wrt. breaking changes: https://github.com/jquery/jquery-ui/commit/68fda5beb2035faa1e30f26722417...

  • Status changed to Downport about 1 month ago
  • πŸ‡¬πŸ‡§United Kingdom catch

    Re-opening for the backport discussion.

  • πŸ‡ΊπŸ‡ΈUnited States xjm

    I'm unsure about backporting this. We did discuss the D10 support timeline with @m_gol and they seemed comfortable with it (thanks @m_gol!)

    Also, if we were to backport it, it should possibly be done in 10.3 for parity with 11.0... except that dependencies don't usually have parity, so that is more of a "should-have" I think. 10.4 is also going to be a maintenance minor β†’ (our first), so changes going into it should restrict disruption. OTOH keeping the maintenance minors' dependencies in sync with the D11 series is part of what they're for, so if the changes are more minor-ish than major-ish from a semver perspective, maybe we could backport it with the compact mode change and a detailed release note about jQuery 1.14.

    One thing we need to pay attention to is if jQuery 1.14's dropped older jQuery version support is compatible with our release cycle and how that would affect maintenance releases (though the info is useful for D11 as well). I.e., How behind are we on jQuery minors? Frequently, the security team has to write emergency bridge code to update to a new jQuery version and/or fork the fix into core when we're on the previous jQuery minor and a JQuery minor update is too disruptive for a security window. So we should check the currently supported versions for each branch, and also go back historically and look at the latency between our jQuery minor version bumps each time.

    Tagging for FFM and RM review on whether to backport.

  • πŸ‡¬πŸ‡§United Kingdom catch

    OTOH keeping the maintenance minors' dependencies in sync with the D11 series is part of what they're for, so if the changes are more minor-ish than major-ish from a semver perspective, maybe we could backport it with the compact mode change and a detailed release note about jQuery 1.14.

    Yeah this is what I was thinking.

    I.e., How behind are we on jQuery minors?

    10.1.x is on jQuery 3.7.0
    10.2.x is on jQuery 3.7.1
    10.3.x is on jQuery 3.7.1

    3.7.1 was released in August 2023 https://blog.jquery.com/2023/08/28/jquery-3-7-1-released-reliable-table-...

    10.2.0 was released in December 2023. So at least last time, we successfully got onto the next jQuery minor release as soon as possible (i.e. our next minor release window).

Production build 0.69.0 2024