Tag Archives: core-css

Dan Farrow 9:20 pm on October 27, 2021
Tags: 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

Dan Farrow 4:56 pm on October 21, 2021
Tags: core-css,   

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

Dan Farrow 8:46 pm on October 12, 2021
Tags: core-css,   

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

Dan Farrow 5:59 pm on October 6, 2021
Tags: core-css,   

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

Dan Farrow 6:56 pm on September 30, 2021
Tags: , core-css   

CSS Chat Agenda: September 30, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, September 30 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 3:49 pm on September 21, 2021
Tags: core-css,   

CSS Chat Summary: 16 September 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @dryanpress shared the working document and the trac ticket, for anybody new to the project
  • All coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have now been claimed, and are either in progress or have a PR, however @dryanpress reminded us that if anyone has claimed a file and can no longer work on it please do let us know
  • The next step is reviewing and merging PRs. Help is very welcome if anybody is up for “trying out a PR and making sure the colors still look correct (or correct enough, where maybe we made changes)“
  • @dryanpress raised the topic of skinning adminadmin (and super admin) colour schemes, as there are some custom properties for body.admin-color-ectoplasm already in custom-properties.css. We would probably create a couple of colour schemes at a later stage, for testing & demonstration purposes
  • @dryanpress outlined the final todo list for the project:
    • Merge all remaining files
    • Look for duplication and opportunities for property consolidation
    • Final team review
    • Merge proposal write-ups
  • @ryelle added that, before the final team review step, discussion will be needed about what to consolidate and how, for example rgba and box-shadow values
  • @ryelle added that, as there are several PRs now merged, anybody interested could start generating some ideas for these next steps right now
  • @dryanpress asked if we are still on target for an --experimental release in 5.9 which @ryelle confirmed we have good momentum for
  • @ryelle observed that there are other places outside of CSS files where CSS is used, for example php and js files, which also need to be reviewed. @dryanpress offered to add this and the other tasks (mentioned above) to the planning document
  • @CodeXplorer admitted to wanting to help but feeling lost, to which @dryanpress provided a few notes of the current state of the project
  • @danfarrow had quickly calculated there are now 127 custom properties in custom-properties.css. @robertg added that this isn’t including the 225 (approx) in his PR

Open Floor / CSS Link Share

Thanks everybody!

#core-css, #summary

Dan Farrow 8:37 am on September 14, 2021
Tags: core-css,   

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

Thanks everybody!

#summary

Dan Farrow 5:44 pm on September 9, 2021
Tags: , 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,   

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