CSS Chat Summary: 02 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. @danfarrow facilitated and wrote up these notes.

Announcements & Housekeeping

@danfarrow shared a document he worked on after last week’s meeting: a CSS Chat Facilitator’s Guide
The document includes a facilitator schedule – anybody interested in running a future CSSCSS Cascading Style Sheets. Chat or CSS Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session is very welcome to add their name!
@notlaura let us know that her attendance will be spottier than usual for the next couple of months, but we are lucky to have had some new attendees join the meetings recently

CSS Custom Properties (#49930)

@robertg asked about indicating pull requests in the planning document’s Claimed & Unclaimed Files list. @danfarrow clarified that they should be marked with a link “Pull request” linking to the PR on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. Merged PRs are indicated by striking through the entire line
@Erik raised the subject of polyfilling, as the ticketticket Created for both bug reports and feature development on the bug tracker. mentions Internet Explorer. @danfarrow pointed out that the ticket was created before WordPress dropped IE support so it’s no longer an issue. It’s always fun to be reminded of this fact, so thanks @Erik!
@robertg shared his WIP PR adding custom properties to customize-controls.css, which is littered with border-* properties
@ryelle announced that anybody who has claimed a file but not been able to work on it is free to unclaim it, with no strings attached. @danfarrow welcomed this sentiment as he may well fall into this categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.
@danfarrow noted that all but 2 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have been claimed, and 11 PRs have been merged. He asked about the next step to which @ryelle responded that we will want to circle back to the unresolved subject of handling colours with opacity
@Erik noted an rgba based approach e.g. background: rgba(var(--color--), .9); which led to an interesting threaded discussion on the subject
@danfarrow asked @ryelle about progress in relation to her projected roadmap. @ryelle responded that at the current pace things are looking good

On that encouraging note the meeting drew to a close. Thanks everyone!

#core-css, #summary

Welcome!

Communication

Announcements & Housekeeping

CSS Custom Properties (#49930)

Share this: