CSS Chat Summary: 30 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.

Housekeeping

The next CSSCSS Cascading Style Sheets. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and CSS Chat on Thursday October 07 at 21:00 UTC are both in need of a facilitator. If you are able to help with either of these please let us know in #core-css or add your name to the schedule in our CSS Chat meeting facilitator’s guide – thank you!

CSS Custom Properties (#49930)

@dryanpress suggested that, once all the PRs are merged, it would be very helpful to add a Table of Contents (TOC) to custom-properties.css. @ryelle agreed that it would help with reducing duplicates and with documentation.
@danfarrow asked about how the TOC sections would be broken down and @dryanpress suggested starting with a Theme and a General section, then adding sections for each file
We discussed following up on unfinished PRs. @dryanpress offered to gently nudge the relevant authors after which we would give them 5 days to respond before picking up / taking over their PRs. @wazeter agreed that applying a soft deadline is a good idea. UPDATE: By the end of the meeting all authors had effectively been nudged!
@danfarrow brought up the issue of rgba colour values and asked what the currently preferred approach is. After an interesting discussion the consensus was that the custom properties should be added for each distinct rgba value, for example --wp-admin--surface--box-shadow: rgba(0, 0, 0, 0.1);. We could then work on a second pass to reduce the number of distinct rgba values.
@joyously imagined a script that sequentially sets each custom property to hotpink, so the user can verify that the visual changes meet expections. UPDATE: Within a few hours @costdev pretty much delivered the goods – amazing!

Open Floor / CSS Link Share

@dryanpress shared a link to a tweet announcing that the ouline ring now automatically adapts to the element border-radius “in the latest releases of all major browsers”
@ryelle shared a link to WordCamp US [Now over, but there’s always next year!]
@dryanpress shared a link to Omatsuri, an essential collection of very useful browser-based HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers., CSS, SVG & other web related tools

Thanks everybody!

#summary

Welcome!

Communication

Housekeeping

CSS Custom Properties (#49930)

Open Floor / CSS Link Share

Share this: