CSS Chat Summary: 18 November 2021

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

Announcements & housekeeping

  • The next meeting will be on Thursday 25 November at 17:00 UTC. Please add your name to the Meeting Facilitator schedule document if you would like to contribute by facilitating this or any future meetings
  • @notlaura suggested breaking for holidays after December 16th and starting up again January 6th 2022
  • @khoipro pointed out that the new meeting time is midnight in APAC which led to a short discussion about meeting times. The conclusion was that we can revisit the meeting time again in the future

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Thanks everybody!

#core-css, #summary

CSS Chat Agenda: November 18, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, November 18, 2021, 12:00 PM EDT in the #core-css channel in Making WordPress 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/.. If there are any other topics you’d like to discuss, please leave a comment on this post.

Meeting Agenda

  • Welcome
  • Announcements & housekeeping
    • Revisit facilitator schedule
  • CSS Custom Properties (#49930)
  • CSS Audit Improvements & other projects
  • Open floor / CSS link share

See you there!

#agenda, #core-css

CSS Chat Summary: 11 November 2021

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

Announcements & housekeeping

Meeting time

  • Last week we initially discussed updating the meeting time to suit people’s schedules better. This week we discussed it further and agreed to try 17:00 UTC.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. will remain on the first Thursday of the month but will now start at 18:00 UTC
  • The next meeting will be on Thursday 18 November at 17:00 UTC. Please add your name to the Meeting Facilitator schedule document if you would like to contribute by facilitating this or any future meetings
  • We’ve added a new Notetaker column to the facilitator schedule – please add your name if you would like to write up the meeting notes! @danfarrow offered to act as a fallback notetaker if nobody else steps forward

CSS Custom Properties (#49930)

  • Last week we discussed updating the targeted release to 6.0, which would give us an --experimental deadline of early next year, unless we manage to get testing done early in the release

CSS Audit project

  • @joyously had asked about the format of colour values in the CSS Audit report and if visibility could be improved. @danfarrow suggested that the values could be moved to appear beneath the colour “chips”
  • @danfarrow also suggested that improvements could be made to the report. Since the report deals with tabular data we could use HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tables in conjunction with a table library like Filament Group’s Tablesaw to enable responsive, sortable tables
  • @notlaura raised the topic of CSS linting, linking an older comment from @tellthemachines pointing out the core CSS doesn’t adhere to our custom WP config. @ryelle clarified that GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ is, but not core CSS, and shared ticket #29792 (she added that getting it implemented would involve fixing 6,000+ errors – yikes!)

Thanks everybody!

#core-css, #summary

CSS Chat Agenda: November 11, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, November 11, 2021, 4:00 PM EDT in the #core-css channel in Making WordPress 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/.. If there are any other topics you’d like to discuss, please leave a comment on this post.

Meeting Agenda

  • Welcome (21:00pm UTC)
  • Announcements & housekeeping
    • Discuss meeting time
  • CSS Custom Properties (#49930)
  • CSS Audit Improvements & other projects
  • Open floor / CSS link share

See you there!

#agenda, #core-css

CSS Chat Summary: 04 November 2021

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

Announcements & housekeeping

  • @notlaura noted some recent facilitator problems and asked for ideas to improve the situation, suggesting:
    • Continue as we are, with the chance of missed meetings
    • Take a winter break
    • Change the meeting frequency
  • @ryelle responded that the meeting have been helpful to coordinate the custom properties project but maybe the time doesn’t work so well for people, plus the EU daylight savings time change may have caused some disruption

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @ryelle reported that there are still some open PRs to review, and also possibly some files that need to be re-claimed. It also looks unlikely that we’ll make the deadline for 5.9
  • @ryelle added that the planning doc has tasks for late September 2021 which she thinks are still valid. She hopes that we can get some momentum up for 6.0
  • @notlaura agreed that aiming for 6.0, and perhaps revising the meeting time, could help pick up some momentum

Thanks everybody!

#core-css, #summary

CSS Chat Agenda: November 4, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, November 4, 2021, 05:00 PM EDT in the #core-css channel in Making WordPress 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/.. If there are any other topics you’d like to discuss, please leave a comment on this post.

There will also be a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. starting at 20:00pm UTC, an hour before the meeting.

Meeting Agenda

  • Welcome (21:00pm UTC)
  • Announcements & housekeeping
  • CSS Custom Properties (#49930)
  • Open floor / CSS link share

See you there!

#agenda, #core-css

CSS Chat Summary: 21 October 2021

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

The meeting was short but props are due to @dryanpress for finding a way to run it despite having no internet!

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Thanks everybody!

#core-css, #summary

CSS Chat Summary: 14 October 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @wazeter shared the planning document and noted that we’re in the final stages of migrating existing colour properties to CSS custom-properties
  • @dryanpress is working on reducing the huge number of custom properties in customize-control.css, a process which has revealed hex values shared by multiple properties. These could effectively be replaced by additional theme properties
  • @wazeter noted that sometimes in larger files it’s better to avoid find-and-replacing colour values and instead to go through logical property groupings e.g. box-shadows, then background etc.
  • @wazeter shared a link to every-layout.dev which outlines an approach to CSS architecture which could be relevant to this project, and which demonstrates the need for a good set of default custom properties
  • This led to a conversation about the next steps, in particular the documentation and Table of Contents (TOC) which will accompany the custom-property roll-out

Thanks everybody!

#core-css, #summary

CSS Chat Summary: 07 October 2021

The meeting took place here on Slack. Thanks to @dryanpress for stepping in to facilitate at the last minute! @danfarrow wrote up these notes.

Housekeeping

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @dryanpress reported that @circlecube has updated comments on his PRs and has been pinged about outstanding merge conflicts
  • @dryanpress is working on .customize-controls.css, continuing @robertg’s extensive work on this 3000 line file
  • @wazeter and @dryanpress reflected on the Custom Property project’s ongoing achievements, made possible by the many generous contributors
  • @dryanpress restated some points from last week’s meeting:
    • custom-properties.css needs organising and the addition of a table of contents
    • box-shadow declarations should be put into custom property
    • This is still the first-pass – there will be further consolidation of the custom-properties

Open Floor / CSS Link Share

Post-meeting chat!

Thanks everybody!

#core-css, #summary

CSS Chat Summary: 30 September 2021

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

Housekeeping

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