CSS Chat Summary: 08 April 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • Our next bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub will be on 22 April at 8pm UTC. If anyone is interested in leading it please let us know in the #core-css channel

Discussion: CSSCSS Cascading Style Sheets. deprecation path

  • The issue initially came up via this ticket and will grow as we start to introduce custom properties into the WP Adminadmin (and super admin) CSS
  • @helen previously outlined an approach in this post – deprecated CSS would be moved to a deprecated file that plugins can still optionally enqueue. It would be helpful if it could run standalone, and if an example of how to implement and run it could be provided e.g. as a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Action workflow
  • Deprecated CSS would generally be at the selector level
  • @sabernhardt provided the recent examples of .icon16 (raised in #35717) and .wp-ui-text-icon
  • We agreed that .icon16 would be a good deprecation candidate to test the process
  • @notlaura suggested adding deprecated selectors to a disallowed list in stylelint, and a PostCSS script to build the deprecated.css stylesheet. PostCSS & stylelint could share the same config file to track deprecated selectors
  • @Ahmed Saeed suggested adding a deprecation notice as a CSS custom property which would be discoverable in dev tools
  • @ryelle added that we would probably want multiple ways to flag deprecated CSS and @tellthemachines agreed it would need to be part of the build process
  • @notlaura suggested a deprecated-with-warnings.css file which is enqueued if WP_DEBUG is on
  • @ryelle clarified the two parts of the problem: identifying the deprecated CSS, and developing external tools for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developers

Next step

  • The next step would be writing a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. outlining the solution & raising it in dev chat
  • @tellthemachines offered to write the ticket

Discussion: CSS naming and usage conventions for JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. targeting (#40686)

  • The intention is to establish a convention for naming CSS classes which are intended for use with JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.
  • There was some discussion to clarify the problem, but in relation to CSS deprecation we need to ensure we’re not deprecating CSS classes that are used by JavaScript
  • We agreed that a js- prefix would clarify that a particular classname is intended for JavaScript interaction

Open Floor + CSS Link Share

  • CSS Audit (#49582) @ryelle has updated the readme & started the process of transferring the repo over to the WordPress org
  • Custom property naming @ryelle has started drafting a make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post about the custom property naming discussions which she’ll share in the channel before posting
  • @danfarrow reminded us that April 09 is the annual CSS Naked Day!

Thanks everyone!

#summaries