CSS Chat Summary: 09 September 2021

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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

Announcements & Housekeeping

@wazeter shared the facilitator schedule sign-up form – please add your name if you would like to run a future meeting or CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
@danfarrow shared the dev-chat meeting guide which could be useful for finishing the Core CSS meeting guide
@danfarrow observed that some WordPress docs pages relating to local dev have not been updated to include details of wp-env and expressed an intention to remedy that

CSS Custom Properties (#49930)

@dryanpress has some files ready to submit, @wazeter is finishing updating media-views.css and @danfarrow posted a draft PR for forms.css
deprecated-media.css is the only remaining unclaimed file
@ryelle has been working on reviewing & merging PRs as they come in. She is planning to open a new base 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"., once more PRs are merged, to make it cleaner for the next stages
@danfarrow asked about the PR review process. @ryelle said she’s been trimming down custom properties to existing ones where possible, and testing in the browser
@danfarrow asked if creating a custom-properties aliasing existing custom-property is ever useful. @ryelle responded that they might be if there could be a requirement to style a component differently, but the subject is open to discussion. @dryanpress & @wazeter expressed the view that more aliases give users more granular control outside of the cascade
There was general agreement that this project is a good opportunity to clean up things like the inheritance structure, minor colour variations etc.

Open Floor / CSS Link Share

@danfarrow shared a link about the new accent-color property now in Chrome & Firefox
@dryanpress shared a CSS Tricks article on the story behind TryShape
@danfarrow shared a bit of web history: Why are hyperlinks blue?
We enjoyed a moment of nostalgia about the bad old days of the web, which led @wazeter to speculate about starting a casual WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS blogblog (versus network, site)
@dryanpress suggested, as a stepping stone to a blog, using the #core-css channel more between meetings

Thanks everybody!

#summary

Welcome!

Communication

Announcements & Housekeeping

CSS Custom Properties (#49930)

Open Floor / CSS Link Share

Share this: