Chat Summary: 16th April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1587071014211100

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

@isabel_brison gave an update on the screehshot testing work in (49606)[https://core.trac.wordpress.org/ticket/49606] and mentioned it proving troublesome to pass the Travis build, and that would be a secondary concern. The most useful part of the tests will be when we are actually making changes to the code and checking for breakage vs. running them on every changeset. I clarified that the workflow would be something like first, generate/update the reference screenshot to contain any changes, and second, run the tests as you develop to check for unintentional changes.

@ryelle shared a custom script for running various audits: https://github.com/ryelle/css-audit – this is a big step for ticket (49638)[https://core.trac.wordpress.org/ticket/49638] and determining the audit methodology. @ryelle‘s scripts are organized by categories like colors, selectors, and important, and each audit outputs a set of data points. The current script outputs audit results in a .txt file, and I mentioned that could certainly be updated to JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. or another format that can be displayed on WP.org or elsewhere. Very cool!

I also pointed out a few tickets mentioned by @isabel_brison on the last chat summary regarding IE 11 hacks. When looking into audit data points for IE hacks or “outdated layout practices”, these would be good to reference: https://core.trac.wordpress.org/ticket/46015, https://core.trac.wordpress.org/ticket/49696 (but if the patch for 46015 makes it through, we have no need for an audit data point!)

Open Floor

I noted a message from @kburgoine regarding experience with IE11 support and color schemes – it’s not necessarily a straightforward task! @isabel_brison mentioned that there may be existing color scheme tickets and that the global styles work in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ includes custom properties. @sabernhardt mentioned the admin color schemes repo from @ryelle and a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. started for Dark Mode. I suggested a boldly titled ticketticket Created for both bug reports and feature development on the bug tracker. “Replace wp-adminadmin (and super admin) color schemes with CSS custom properties” so that we can track the conversation, and responses were positive!

That was all for this week!

#summary #core-css