#43195 closed enhancement (fixed)
dashicons fail w3c css validation
| Reported by: | manuel_84 | Owned by: | SergeyBiryukov |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.1 |
| Component: | Administration | Version: | 4.9.2 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: | ui, coding-standards |
Description
/wp-includes/css/dashicons.min.css?ver=4.9.2
line 2: .dashicons, .dashicons-before:before
0 is not a value for transition : color 0.1s ease-in 0
Attachments (1)
Change History (14)
#2
@
9 years ago
Thank you @manuel_84 for opening your first ticket :-)
Good catch with the bug.
An alternative solution would be to drop the transition-delay completely since the default is 0s anyway:
transition: color 0.1s ease-in;
#3
@
9 years ago
- Component Bundled Theme → Administration
- Focuses template removed
- Milestone Awaiting Review → 5.0
#5
@
9 years ago
Per https://developer.mozilla.org/en-US/docs/Web/CSS/time:
Although unitless zero is allowed for
<length>s, it's invalid for<time>s.
#7
@
9 years ago
Created a GitHub issue for genericons.css: https://github.com/Automattic/Genericons/issues/109, since it's bundled with Twenty Fifteen and Twenty Sixteen.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
fix by adding a "s" after the final 0:
transition : color 0.1s ease-in 0s