CSS Chat Summary: 26th March 2020

Full meeting transcript on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.: https://wordpress.slack.com/archives/CQ7V4966Q/p1585256425000800

I (@isabel_brison) facilitated the meeting. 

CSSCSS Cascading Style Sheets. audit updates

• I looked into our possibilities for visual regressionregression 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 and found that jest-image-snapshot integrates very well with our existing e2e testing tools. I’m preparing a prototype branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". that I will share on the ticketticket Created for both bug reports and feature development on the bug tracker. soon.

Open Floor

@sabernhardt requested feedback on a patch for adding print styles to wp-admin. Discussion ensued, and we agreed that:

• Currently, when printing out wp-adminadmin (and super admin), the only thing that doesn’t show is the admin bar. This is not optimal, and print styles should remove all interface features not relevant to page content.

• The print styles should apply to all wp-admin pages that have content and/or lists.

• Work on the initial ticket should attempt to hide all common interface elements for print

• If much further work is needed on individual pages, we should create sub-tickets for easier tracking/review.

And that was all for this week!

#core-css, #summary