Make WordPress Core

#57555 closed task (blessed) (fixed)

Update `caniuse` data for 6.2

Reported by: desrosj's profile desrosj Owned by:
Milestone: 6.2 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: has-patch
Focuses: Cc:


This ticket is for tracking updates to the caniuse data and documenting resulting changes throughout the 6.2 cycle.


Change History (8)

#1 @desrosj
18 months ago

In 55137:

Build/Test Tools: Update caniuse-lite to the latest version.

This updates the caniuse-lite database from 1.0.30001407 to 1.0.30001448 and applies the resulting changes to generated WP Admin CSS.

This removes two occurrences of -o-tab-size, which was required for partial support of the tab-size property in Opera Mini. Usage has dropped below 1%, hence this vendor prefix being removed.

See #57555.

#2 @desrosj
18 months ago

In 55139:

Build/Test Tools: Revert [55137].

This changeset resulted in some unexpected JavaScript validation failures.

See #57555.

#3 @desrosj
18 months ago

I'm not sure exactly what's causing the failure here yet, but it seems like the break happens in caniuse-lite > 1.0.30001436.

Because the changes in #57554 resulted in -o-tab-size being removed, I wanted to commit that separately. But I will just include that change there and the issue with newer caniuse-lite versions can be investigated further.

#4 @desrosj
18 months ago

In 55150:

Build/Test Tools: Update PostCSS to version 8.

This updates PostCSS related dependencies for the main Core build process to versions that use the latest major version of PostCSS, 8.x.

There were no changes to any versioned CSS files as a result of this update directly. However, two occurrences of -o-tab-size have been removed due to the version of caniuse-lite used being updated in the process.

See #57554, #57555.

This ticket was mentioned in PR #4005 on WordPress/wordpress-develop by @sakibmd.

18 months ago

  • Keywords has-patch added

Updated caniuse from v1.0.30001407 to v1.0.30001450

Trac ticket:

This ticket was mentioned in Slack in #core by costdev. View the logs.

17 months ago

#7 @hellofromTonya
17 months ago

Opened #57856 for the ongoing work into the 6.3 cycle.

#8 @desrosj
17 months ago

  • Resolution set to fixed
  • Status changed from new to closed

I've tested this again today and it seems that the same problem described above still exists, even after some additional releases have been pushed out.

There are no browser support policy changes as a result of updating to the latest version, so I'm going to close this one out as fixed. We can troubleshoot this in #57856 when there are changes to built files resulting from a change in the target browsers.

Note: See TracTickets for help on using tickets.