[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 isabel_brison):

 > I think the deprecated file is a good way to iteratively move forward -
 a way to improve the CSS without an entire redesign. It would need to
 always be enqueued though, to support the plugins that haven't been
 updated.

 Hmmm, my thought when suggesting this was that the main advantage would be
 performance gains from serving less code. If that's not going to happen,
 there's not a huge point in extracting deprecated CSS to another file - we
 could just move it to a "Deprecated" section at the bottom of its current
 file. That will provide pretty much the same DX improvement as a separate
 file, with a lot less work on our side :)

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