Full meeting transcript here on slack. @notlaura facilitated the meeting & @danfarrow wrote up this summary.
@notlaura reminded everybody to complete the WordPress 2020 survey – it takes less than 10 minutes so if you haven’t already done so, you know what to do!
CSS Cascading Style Sheets. Audit (#49582)
@notlaura reported nearing completion of her PR to add config file functionality to the audit tool, as discussed in previous meetings.
@notlaura agreed with last week’s conclusion that the audit report needs a little refinement before being shared on the
!important audit ticket Created for both bug reports and feature development on the bug tracker., #26350. @sabernhardt consequently offered to update that ticket’s milestone to 5.7, which was welcomed.
Color Scheming (#49999)
@notlaura contributed some valuable insights to last week’s discussion (which she had been unable to attend) about visual regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. testing being a potential stumbling block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for #49999.
She clarified that visual regression testing had been discussed right at the start of the CSS Audit project, back in March, and drew our attention to a ticket opened by @isabel_brison #49606 Add visual regression testing to core.
@isabel_brison also submitted a PR to integrates visual regression testing into e2e core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tests, using
jest-image-snapshot. In the most recent comment however she concluded that visual regression testing might be better implemented as a separate script to be run locally, rather than part of the e2e core test suite.
Back in the meeting, @notlaura suggested that checking out this PR might be a good starting point to continue exploring the subject. @danfarrow (me!) offered to look into this, despite not really knowing what’s involved. Only time will tell if his eagerness to contribute is misplaced!
@notlaura suggested adding a new agenda item for visual regression testing, to which @danfarrow agreed.
Further to last week’s discussion, @notlaura agreed that seeking feedback on the color scheming tests should be deprioritised until the release of 5.6.
CSS links share + Open floor
@danfarrow shared a link to a processor intensive (in Firefox at least – it’s not so bad in Chromium) CSS only puzzle game where the goal is to click blocks in order to build a lighthouse before night falls.
@notlaura shared a link to an MDN page about CSS Logical Properties and Values.
CSS Logical Properties and Values is a module of CSS introducing logical properties and values that provide the ability to control layout through logical, rather than physical, direction and dimension mappings.
This module introduces many new properties and values into CSS which may soon be encountered in the wild, so it’s good to get a heads-up on what they’re all about.
And with that the meeting was concluded. Thanks all!