[wp-trac] [WordPress Trac] #53070: Establish a Core CSS deprecation path

[WordPress Trac]

#53070: Establish a Core CSS deprecation path
---------------------------+-------------------------------
 Reporter:  isabel_brison  |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  General        |     Version:
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  css, performance
---------------------------+-------------------------------

Comment (by audrasjb):

 Hello there,

 That's a nice idea.

 But I have a dummy question :)
 My concern is about the way we should handle deprecation history for a
 given CSS selector (or CSS rule).

 Let's say, for example we have this in WP 5.7:
 {{{
 /** CSS File: example.css */
 .example {
     font-size: 1em;
 }
 }}}

 In WP 5.8 we decide to change the font size, and we start to maintain the
 `deprecated.css` file:
 {{{
 /** CSS File: example.css */
 .example {
     font-size: 1.5em;
 }
 /** CSS File: deprecated.css */
 .example {
     font-size: 1em; // @deprecated 5.8.0
 }
 }}}

 Finally that was a bad idea, so in WP 5.9, we need to use a different font
 size again:
 {{{
 /** CSS File: example.css */
 .example {
     font-size: 2em;
 }
 /** CSS File: deprecated.css */
 .example {
     font-size: [what's the best value here? 1em or 1.5em???]; //
 @deprecated 5.9.0
 }
 }}}

 Should we only maintain the last major release's version of each CSS rule
 or declaration?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53070#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform