The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes (I’m trying a more bullet-pointy format this time – hope you like it!)
@kburgoine has volunteered to lead next week’s bug 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 which will begin at 9pm UTC on Thursday 29 January.
CSS Cascading Style Sheets. Audit (#49582)
- @ryelle is ready to merge some recent PRs on the audit tool [UPDATE now done, thanks!]
- @notlaura is considering ideas for restructuring the property-values audits within the config file
- @notlaura later mentioned that the
!important audit report probably satisfied the requirements of #26350 and suggested that @kburgoine could bring it up at next week’s bug-scrub
Color Scheming (#49999) & 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 (#49606)
- @ryelle has had some feedback on her reduced colours PR and is hoping for one more nod from Design so she can commit in the next few days
- @ibdz kindly offered to provide feedback this weekend
- Next step for #49999 would be more CSS cleanup, plus picking up the previous conversations around design system, tokens & custom properties
- @tellthemachines PR for #49606 is ready for testing – let’s go!
Open floor & CSS link share
- @ryelle brought up #51763, a ticket Created for both bug reports and feature development on the bug tracker. about moving from
dart-sass, which needs a patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. @desrosj has offered assistance and @ryelle is happy to partner with anyone interested in helping
- @notlaura shared a link to this CSS WG thread discussing ideas for expressing
@media conditional values more tersely
- @notlaura also shared this CSS WG thread about SCSS stats in the wild, with data analysis based on 300K SCSS stylesheets revealing that “inline
if() is the second most used function (after
darken() ) and accounts for 14.5% of all function calls“
Thanks everyone for attending this week!