[wp-trac] [WordPress Trac] #53070: Establish a Core CSS deprecation path
WordPress Trac
noreply at wordpress.org
Thu Dec 16 21:18:34 UTC 2021
#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 ryelle):
In the PR for #54489, I tried a pass at specifically marking things
deprecated (and why). For example,
{{{
/* @deprecated 5.9.0 -- Button removed from panel. */
.wp-core-ui .welcome-panel .button.button-hero {
...
}}}
You can see more deprecated comments [https://github.com/WordPress
/wordpress-develop/pull/2049/files in the PR itself], the new markup is
much simpler so it cuts down a lot of CSS. I went with this format because
it can eventually be read by a script, with the version and description
separated with double hyphen (inspired by [https://stylelint.io/user-guide
/ignore-code/ stylelint's ignore comments]).
I'm not totally sure how it could be used just yet, but I think setting up
a format like this would be a good start. Even if it never ends up
scripted, at least having a note about what CSS is still relevant is
useful.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53070#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list