Project

General

Profile

Actions

Feature #33383

closed

Update jQuery to 3.5.1

Added by Marius BĂLTEANU almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Third-party libraries
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

jQuery 2 is end of life and we should update the code to support latest jQuery 3.5.0 (at this time).


Files


Related issues

Related to Redmine - Patch #33384: jQuery: replace deprecated size() method with length ClosedGo MAEDA

Actions
Related to Redmine - Defect #33392: Fix invalid selector in function displayTabsButtons()ClosedGo MAEDA

Actions
Related to Redmine - Defect #33896: Incorrect position of the revision graphClosedGo MAEDA

Actions
Related to Redmine - Feature #34337: Remove jQuery MigrateClosedGo MAEDA

Actions
Related to Redmine - Patch #35729: Update jQuery to 3.6.0ClosedMarius BĂLTEANU

Actions
Actions #1

Updated by Marius BĂLTEANU almost 4 years ago

  • Related to Patch #33384: jQuery: replace deprecated size() method with length added
Actions #2

Updated by Marius BĂLTEANU almost 4 years ago

  • Related to Defect #33392: Fix invalid selector in function displayTabsButtons() added
Actions #3

Updated by Marius BĂLTEANU almost 4 years ago

Here are two patches that update jQuery to 3.5.1 and fix a problem caused by this change.

Because the update can break some plugins, I propose the following plan for this update:
  1. Commit the current patches
  2. Keep this ticket open for one or two months in order to have time to find potential problems generated by the update
  3. After this period, commit jQuery Migrate
  4. In Redmine 5.0.0, remove jQuery Migrate and keep only the latest jQuery version.
Actions #4

Updated by Go MAEDA almost 4 years ago

Thank you for working on updating JQuery.

Marius BALTEANU wrote:

Because the update can break some plugins, I propose the following plan for this update:
  1. Commit the current patches
  2. Keep this ticket open for one or two months in order to have time to find potential problems generated by the update
  3. After this period, commit jQuery Migrate

I agree. In order to make enough time to discover and fix issues caused by the update, I think it is better to commit the patches as soon as we can.

Do you think it is OK to commit the patches right now?

Actions #5

Updated by Go MAEDA almost 4 years ago

  • Target version changed from Candidate for next major release to 4.2.0

I think it is better to commit this patch as soon as possible in order to detect problems early. Setting the target version to 4.2.0.

Actions #6

Updated by Go MAEDA almost 4 years ago

  • Status changed from New to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patches. Thank you.

Actions #7

Updated by Marius BĂLTEANU almost 4 years ago

Go MAEDA wrote:

Thank you for working on updating JQuery.

Marius BALTEANU wrote:

Because the update can break some plugins, I propose the following plan for this update:
  1. Commit the current patches
  2. Keep this ticket open for one or two months in order to have time to find potential problems generated by the update
  3. After this period, commit jQuery Migrate

I agree. In order to make enough time to discover and fix issues caused by the update, I think it is better to commit the patches as soon as we can.

Do you think it is OK to commit the patches right now?

Sorry for my late reply, yes, it's ok to have the patches committed.

Actions #8

Updated by Go MAEDA over 3 years ago

  • Related to Defect #33896: Incorrect position of the revision graph added
Actions #9

Updated by Go MAEDA over 3 years ago

Marius BALTEANU wrote:

Because the update can break some plugins, I propose the following plan for this update:
  1. Commit the current patches
  2. Keep this ticket open for one or two months in order to have time to find potential problems generated by the update
  3. After this period, commit jQuery Migrate
  4. In Redmine 5.0.0, remove jQuery Migrate and keep only the latest jQuery version.

Six months have passed since upgrading JQuery to 3.5.1. I think it is time to add jquery-migrate. Marius, what is your opinion?

Actions #10

Updated by Marius BĂLTEANU over 3 years ago

Go MAEDA wrote:

Marius BALTEANU wrote:

Because the update can break some plugins, I propose the following plan for this update:
  1. Commit the current patches
  2. Keep this ticket open for one or two months in order to have time to find potential problems generated by the update
  3. After this period, commit jQuery Migrate
  4. In Redmine 5.0.0, remove jQuery Migrate and keep only the latest jQuery version.

Six months have passed since upgrading JQuery to 3.5.1. I think it is time to add jquery-migrate. Marius, what is your opinion?

Yes, let's do it.

Actions #11

Updated by Go MAEDA over 3 years ago

Actions #12

Updated by Go MAEDA over 3 years ago

  • Status changed from Resolved to Closed
  • Assignee changed from Marius BĂLTEANU to Go MAEDA

Added jQuery Migrate in r20518.

Actions #13

Updated by Marius BĂLTEANU over 3 years ago

We should remove the security fix for jQuery < 3.

Actions #14

Updated by Go MAEDA over 3 years ago

  • Status changed from Reopened to Closed

Marius BALTEANU wrote:

We should remove the security fix for jQuery < 3.

Done in r20709.

Actions #15

Updated by Go MAEDA over 3 years ago

  • Category changed from Code cleanup/refactoring to Third-party libraries
Actions #16

Updated by Marius BĂLTEANU over 2 years ago

Actions

Also available in: Atom PDF