W3C CSS Validator error in some core CSS files

[man4toman]

There is some error related to transition delay value. In some core CSS files the delay values sets on "0" and it's incorrect, it must be "0s".

The related patches is for these files:

wp-admin/css/common.css
wp-admin/css/themes.css
wp-includes/css/dashicons.css

[man4toman]

common.css

[man4toman]

themes.css

[man4toman]

dashicons.css

[man4toman]

W3C CSS Validator

[swissspidy]

Would you mind creating the patches from the root of your WordPress development directory so that patch files contain the full paths? Makes it easier to apply the changes locally :-)

[man4toman]

All

[man4toman]

@swissspidy

Hmm, do I understand you? The new patch contain all files paths.

[mukesh27]

@man4toman, updated patch as you have missed rtl css files.

[man4toman]

@mukesh27 Thanks but I remember @netweb told me there isn't need to patch RTL codes because they use RTLCSS to generate RTL files, so I didn't add codes for RTL.

Then I think the first patch file is OK.

[netweb]

Replying to man4toman:

@mukesh27 Thanks but I remember @netweb told me there isn't need to patch RTL codes because they use RTLCSS to generate RTL files, so I didn't add codes for RTL.

This is correct, the RTL CSS files are automatically generated by the build tools

Then I think the first patch file is OK.

Correct, patch all.patch​ is all that is required

[man4toman]

@netweb
Thanks, I remember what you said to me :)

[mukesh27]

Thanks @netweb. i don't know how rtl css generate.

Replying to netweb:

Replying to man4toman:

@mukesh27 Thanks but I remember @netweb told me there isn't need to patch RTL codes because they use RTLCSS to generate RTL files, so I didn't add codes for RTL.

This is correct, the RTL CSS files are automatically generated by the build tools

Then I think the first patch file is OK.

Correct, patch all.patch​ is all that is required

[swissspidy]

@mukesh27 You don‘t have to do a thing there :-)

[desrosj]

Hi @man4toman,

Thanks for working on this! It appears that this issue was fixed in [42689], though. The changes for #43195 will be released in WordPress 5.1.