Dan Farrow 8:37 am on September 14, 2021
Tags: core-css, summary ( 464 )

CSS Chat Summary: 09 September 2021

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

Dan Farrow 5:44 pm on September 9, 2021
Tags: agenda ( 640 ), core-css

CSS Chat Agenda: September 09, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, September 09 at 21:00 UTC 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/..

Meeting Agenda

Announcements & Housekeeping
CSS Custom Properties (#49930)
Open Floor / CSS Link Share

See you there!

#agenda

Dan Farrow 9:36 pm on September 6, 2021
Tags: core-css, summary ( 464 )

CSS Chat Summary: 02 September 2021

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 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

Dan Farrow 6:25 pm on September 2, 2021
Tags: agenda ( 640 ), core-css

CSS Chat Agenda: September 02, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today, Thursday September 02, at 21:00pm UTC 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/..

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

Dan Farrow 11:59 am on August 29, 2021
Tags: core-css, summary ( 464 )

CSS Chat Summary: 26 August 2021

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

Announcements & Housekeeping

Previously we had talked about rotating the meeting facilitator on a regular basis. @notlaura asked anybody wanting to join the rota to step forward
UPDATE: We’re now working on a Meeting Guide document, which includes a facilitator schedule for people to sign up to

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

@notlaura introduced the project for new attendees and asked for any updates
@wazeter committed two PRs last week, one in coordination with @robertg – more commits coming in a few days!
@dryanpress similarly expects to be committing in the next few days
@ryelle has updated the shared planning document with links to the PRs, and @circlecube has been helpfully indicating merged PRs by ~~striking them through~~
@ryelle asked for help reviewing the PRs – @dryanpress & @wazeter offered their assistance
@wazeter shared some details of his methodology for themes.css where he temporarily moved many custom properties to the top of the file with a prefix --wp-admin--themes
@ryelle noted that all custom properties should eventually be moved into custom-properties.css
@wazeter asked about fallback values which @ryelle responded to: hex fallback rules, which precede rules assigning rgba values for browsers that don’t understand rgba, can now be removed since coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s browser support has been updated – UPDATE: I’ve added a note about this in the shared doc
@notlaura added a final note thanking all contributions, especially newcomers

CSS Link Share / Open Floor

@notlaura raised the topic of meeting structure, in particular keeping the structured work sessions for times when attendance is low
@wazeter supported the meeting format, noting that he sometimes was unsure what to do in the structured work session
@notlaura suggested creating some general guidelines on how to run Core CSS meetings – UPDATE: Now underway here!
@ryelle volunteered to run the CSS triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session before next week’s meeting – thanks @ryelle!

Thanks everyone!

NOTE: For those interested in facilitating a future meeting or triage, please add your name to the Facilitator Schedule here

#core-css, #summary

Lara Schenck 6:29 pm on August 26, 2021
Tags: agenda ( 640 ), core-css

CSS Chat Agenda: August 26, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is Thursday, August 26 at 21:00PM UTC in the #core-css channel in Making WordPress Slack.

CSS Custom Properties (#49930)

Focused on substituting existing colors throughout CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets, the CSS Custom Properties project aims to make working with Adminadmin (and super admin) Themes & Admin Color Schemes easier and more reliable both in Core and Plugins.

The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here). No prior contributing experience is required — we’re happy to assist anyone who would like to participate! This meeting we will continue with work and collaboration, time permitting.

Meeting Agenda

Welcome (21:00PM UTC)
Announcements & Housekeeping
CSS Custom Properties (#49930)
- Overview & Updates
- How to Get Involved
- Status Check-In & Blockers
Work & Collaboration (time permitting)
Open Floor
CSS Link Share (Bring neat examples & helpful tools!)

#agenda, #core-css

Dan Farrow 2:50 pm on August 21, 2021
Tags: core-css, summary ( 464 )

CSS Chat Summary: 19 August 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

@dryanpress outlined the goal of the project: To replace hard-coded colors in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets with CSS Custom Properties
@circlecube & @wazeter are close to posting their contributions
@wazeter asked for (and received!) confirmation that contributions should be submitted as PRs to the try/custom-properties branch of @ryelle’s WordPress Develop fork
@dryanpress posted a project status update:
- This Google Doc is the working document with all the steps
- Work is continuing on (ryelle/wordpress-develop)[https://github.com/ryelle/wordpress-develop/pull/2]
- Last week’s chat summary here covers our discussion around box-shadow, why we can’t use HSL and that we’ll be continuing discussion on this PR
- This project is targeted for experimental release in WordPress 5.9 and then a stable release in 6.0. To make WordPress 5.9, the project probably needs to be merge-ready by end of August
@robertg asked if rgba values should be assigned to custom properties. @dryanpress linked to the PR which has some discussion on that question, noting that rgba values are mostly used in box-shadow. We’ll hopefully soon reach a consensus on this point in the discussion
@ryelle asked for input on this PR about CSS loading & dependencies. @dryanpress replied with a link to an issue he experienced with a partial colour change on the user profile page, and saved values not updating after reload
@dryanpress then announced the start of this week’s <working-time>

Working Time

@robertg has taken on src/wp-admin/css/customize-controls.css which 2900+`lines of CSS. Bon courage Robert!
@wazeter has looked at other contributors change files in order to see how others have approached the problem, which seems like a sensible approach

CSS Link Share / Open Floor

@dryanpress shared a tweet about pending browser support for the experimental accent-color property which would set a custom colour to form elements in one simple CSS rule
@dryanpress also shared a link about Chromium based browsers soon supporting dynamic CSS module imports in JavaScript

Thanks everyone!

#core-css, #summary

Dan Farrow 8:53 am on August 18, 2021
Tags: core-css, summary ( 464 )

CSS Chat Summary: 12 August 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

@notlaura gave an overview of the project, its goals and resources for any new contributors
@dryanpress (fka @Dave Ryan) linked to his PR which introduces some commonly used theme variables to defined colours indicating statuses such as success and error :

   --wp-admin--theme--primary--step-10: #1a5686;
   --wp-admin--theme--notification: #d63638;
   --wp-admin--theme--notification--contrast: #fff;
   --wp-admin--theme--success: #00a32a;
   --wp-admin--theme--info: #72aee6;
   --wp-admin--theme--warning: #dba617;
   --wp-admin--theme--error: var(--wp-admin--theme--notification);

@robertg asked a question about where new custom properties should be defined. @ryelle answered that they should be in custom-properties.css, in the body selector so that they can be overridden by colour themes later

How should `box-shadow`s be handled?

@ryelle introduced the subject of handling box-shadow colour values and shared linked to a PR comment about her current approach
@dryanpress outlined two possibilities for handling opacity / alpha: Defining each rgba value as a single custom-property, or splitting into separate rgb and alpha custom-properties to use with functional rgb notation
@wazeter suggested an HSL based solution. Unfortunately we can’t consider HSL as an option at this stage
@ryelle concluded that the alpha-value discussion can happen later and for now we possibly need some custom-properties for the entire box-shadow value. Further ideas can be added as replies to her PR comment (link above)

Working time

@notlaura started the 20 minute session where contributors can work on the project while having help available in the 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/. channel
@robertg asked if the :hover and :focus pseudo-classes should have separate custom-properties. @ryelle answered that one custom-property can be defined for --hover and also used for :focus
@wazeter asked about the timeline. @notlaura replied that for the 5.9 release we would be aiming for the end of August. @ryelle clarified that this is the target for “early“ consideration. We’ll know the target for the completed project when the real cutoff has been announced but she expects it to be around early-mid October
@notlaura added that next week’s meeting (August 18) is the last scheduled week for working time
@wazeter asked where questions about quirks should be addressed. @notlaura replied post in the #core-css channel or comment in the PR
@robertg asked if we are just targetting color, background-color, and border-colors for now. @notlaura added box-shadow, noting that this will need some additional discussion

CSS Link Share / Open Floor

@dryanpress shared a link to Tailwind Labs video on the concept of isolation, adding that the Tailwind Labs videos generally are a great resource

Thanks everyone!

#summary

David Ryan 1:04 am on August 18, 2021
Tags: agenda ( 640 ), core-css

CSS Chat Agenda: August 19, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is Thursday, August 19 at 21:00PM UTC in the #core-css channel in Making WordPress Slack.

CSS Custom Properties (#49930)

The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here).

No prior contributing experience is required — we’re happy to assist anyone who would like to participate!

Meeting Agenda

Welcome (21:00PM UTC)
Announcements & Housekeeping
CSS Custom Properties (#49930)
- Overview
- How to Get Involved
- Status Check-In & Blockers
Open Floor
Working & Collaboration Time
Huddle Up & Closing Discussion (21:50PM UTC)
CSS Link Share (Bring neat examples & helpful tools!)

#agenda

Lara Schenck 3:36 pm on August 12, 2021
Tags: agenda ( 640 ), core-css

CSS Chat Agenda: August 12, 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday August 21 at 21:00PM UTC. The meeting will be held in the #core-css channel in the 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/..

This week, we will be continuing with a supported working session for new contributors! Please see this post with our call for contributors and more details. Our agenda is as follows:

Welcome
Housekeeping
Discussion around the CSS Custom Properties project (#49930)
- Brief Overview
- How to Get Involved
Open Floor
Working Time
21:50PM UTC – Circle back, closing discussion, CSS link share

#agenda, #core-css

WordPress.org

Welcome!

Communication

Tag Archives: core-css

CSS Chat Summary: 09 September 2021

Announcements & Housekeeping

CSS Custom Properties (#49930)

Open Floor / CSS Link Share

CSS Chat Agenda: September 09, 2021

Meeting Agenda

CSS Chat Summary: 02 September 2021

Announcements & Housekeeping

CSS Custom Properties (#49930)

CSS Chat Agenda: September 02, 2021

Meeting Agenda

CSS Chat Summary: 26 August 2021

Announcements & Housekeeping

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

CSS Link Share / Open Floor

CSS Chat Agenda: August 26, 2021

CSS Custom Properties (#49930)

Meeting Agenda

CSS Chat Summary: 19 August 2021

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Working Time

CSS Link Share / Open Floor

CSS Chat Summary: 12 August 2021

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

How should `box-shadow`s be handled?

Working time

CSS Link Share / Open Floor

CSS Chat Agenda: August 19, 2021

CSS Custom Properties (#49930)

Meeting Agenda

CSS Chat Agenda: August 12, 2021

Welcome!

Communication

Announcements & Housekeeping

CSS Custom Properties (#49930)

Open Floor / CSS Link Share

Meeting Agenda

Announcements & Housekeeping

CSS Custom Properties (#49930)

Meeting Agenda

Announcements & Housekeeping

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

CSS Link Share / Open Floor

CSS Custom Properties (#49930)

Meeting Agenda

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Working Time

CSS Link Share / Open Floor

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

How should box-shadows be handled?

Working time

CSS Link Share / Open Floor

CSS Custom Properties (#49930)

Meeting Agenda

How should `box-shadow`s be handled?