CSS Chat Agenda: 21 January 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, January 21, at 10:00 PM UTC. This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
    • Bug scrub next week
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 14 January 2021

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

Housekeeping

@notlaura pointed out that we missed a scheduled 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. scrub today which started a short discussion about how to make them consistent.

The outcome was that the lead for each scrub should be established the week before which @notlaura will check in with to make sure the scrub can go ahead as planned. If necessary an upcoming scrub can be skipped and removed from the meetings calendar.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported having made a PR to reorganise the audit tool’s HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. report directory structure with the goal of simplification. He also moved the report stylesheet into /src and added a command to copy it into /public, which means that files inside /public need no longer be edited manually.

@notlaura noted that the property values reports issue still needs to be resolved. She linked to this related github issue as a place to discuss & keep track of ideas.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

@isabel_brison shared her PR to add visual regression tests for wp-admin pages which is now ready for review/testing. This will be a very useful addition to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing suite, particularly for CSS.

@ryelle reported that she shared her reduced colours branch in dev chat and is hoping for more feedback, from design especially. To encourage this she also added needs-testing to #49999. The branch is available here – please have a look.

Open floor & CSS link share

@isabel_brison shared a link to Web Directions’ call for speakers for their upcoming CSS conference. The deadline is the end of this month so get those proposals in!

@notlaura shared a useful reference for logical CSS functions min, max and clamp.

@danfarrow shared a piece of CSS esoteria: an ugly hack for rounding values down with two decimal places.

This prompted wry speculation on the usefulness of 0.01px precision, and with that the meeting concluded. Thanks everyone!

#core-css, #design, #summary

CSS Chat Agenda: 14 January 2021

Note: 1 hour before the meeting, we will have the bi-monthly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

This is the agenda for the upcoming CSS meeting scheduled for Thursday, January 14, at 10:00 PM UTC. This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
    • Checking in on meeting format
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 07 January 2021

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

Housekeeping

@notlaura asked if the recurrant format of the meetings is still working and there was general agreement that yes, it is.

CSSCSS Cascading Style Sheets. Audit (#49582)

@ryelle commented that @notlaura‘s config file PR is looking good and that she has started a new PR using GitHub actions to auto-generate the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS audit report.

@notlaura shared a screengrab of an issue with the report’s in-page navigation when used with config files. The full text of each property-value query is being used in the nav making it look quite unwieldy.

This led to a discussion about how property-value audit queries should be formed in order to provide useful results, and then to a recap of the end goals of the audit. The consensus was that one of the main goals is to improve consistency of CSS values, and to identify repeatable patterns which could be abstracted into design-system type naming.

@ryelle clarified that this was the thinking behind audits reporting the top 10 most & least used values.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

@ryelle expressed some doubts over the benefits of the reduced colors branch. The group was quick to dispel these doubts, pointing out several ongoing benefits of the project and assuring her that it’s well worth continuing with.

Bolstered by the positivity, @ryelle said she would refresh the 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". and bring it up at the next dev chat.

Open floor & CSS link share

@ryelle put a call out for testers for patches she has contributed to these three CSS related trac tickets.

@notlaura shared a link to @q‘s 2020 proposal about a global style system, suggesting it would be cool to apply to apply such a system to WordPress adminadmin (and super admin).

And with that inspiring thought the meeting drew to a close. Thanks everyone!

#core-css, #summary

CSS Chat Agenda: 7 January 2021

And we’re back after a couple weeks break!

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, January 7, at 10:00 PM UTC. This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
    • Checking in on meeting format
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 17 December 2020

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

Housekeeping

We discussed the meeting schedule over the next two weeks. There was general agreement that we should take the next two weeks off, so the next meeting will be 07 January 2021. Happy holidays!

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported that we can now add a note to the !important audit ticketticket Created for both bug reports and feature development on the bug tracker. #26350 with a link to the !important audit section of the report (update: this note has now been added here).

Thanks to @sabernhardt‘s comprehensive audit spreadsheet we can see that the number of !important declarations has dropped from 142 at the start of this year to the current 106.

@ryelle reported an issue with the colour counts which means they are slightly off, however in order to fix it would require a major overhaul of the audit process. However, the discrepancy is minor.

@ryelle also noted that colours defined in colour schemes are not currently included in the numbers and suggested that they should be included.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

@ryelle has pushed a PR for reduced colours in core which is one step in her plan outlined in this comment.

She also shared her excellent before & after comparison page built to enable comparison between current & reduced colours.

We agreed that the next step is to bring this up in the first dev chat in January.

For visual regression testing, @isabel_brison suggested that the next step would be to separate the test config from the e2e config to enable them to be run independently.

Open floor & CSS link share

@danfarrow shared an enlightening article on The Surprising Things That CSS Can Animate, from the UI Animation newsletter.

@notlaura shared an excellent CSS Tricks article from Jeremy Keith on “the enjoyment of building a website with plain ol’ HTML, CSS, and JavaScript” which inspired an exchange of thoughts & feelings about web tools.

The conclusion was that our favourite web tool platform is of course ❤️ WordPress ❤️, and on that note the meeting concluded.

Thanks everybody and see you in 2021!

#core-css, #summary

CSS Chat Agenda: 17 December 2020

Note: 1 hour before the meeting this week, @sabernhardt will lead the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

This is the agenda for the upcoming CSS meeting scheduled for Thursday, December 17, at 10:00 PM UTC. This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share
#agenda, #core-css

CSS Chat Summary: 10 December 2020

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

Housekeeping

@notlaura congratulated everyone who worked on the 5.6 release.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow shared his updated version of the audit report (featuring sticky headers & dark mode!)

@notlaura reported having the style property values audit working, and making progress on her config PR which is nearly ready.

@ryelle reported a new PR to tweak report generation in order to decouple audits from specific templates, which would reduce the number of templates required.

Some great progress happening!

Color Scheming (#49999)

@danfarrow reported having fixed his wp-env problems and generated visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. diffs based on the initial PR from @tellthemachines.

We discussed how this feature could be incorporated into wordpress-develop, and agreed that the tests would be best run manually. The discussion concluded with a positive sense that this tool could meet one of the goals of the CSS audit project.

@ryelle reported that her public demo site for reduced adminadmin (and super admin) colours shouldn’t be used at the moment as it needs updating.

Open floor / CSS link share

@notlaura shared a link to Houdini.how, a community-driven resource library to learn about CSS Houdini.

And with that the meeting concluded. Thanks everybody!

#core-css, #summary

CSS Chat Agenda: 10 December 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, December 10, at 10:00 PM UTC. This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 03 December 2020

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

Housekeeping

@notlaura thanked @danfarrow for running last week’s meeting and hoped that US folks had a happy & socially distanced Thanksgiving.

CSSCSS Cascading Style Sheets. Audit (#49582)

@ryelle reported having spent some time on the CSS audit repo, and asked @danfarrow what else he wanted to do before his PR was ready to commit. @danfarrow suggested it could be committed now and he would continue working in a new PR, so @ryelle merged it there and then.

@ryelle mentioned the config PR and posted a link to an npm package cosmiconf that might be useful. @notlaura reported having made some progress on the feature and will have a working version soon.

We had a short discussion about naming the reports in the repo’s /public folder, agreeing that historical reports could include the relevant WordPress release number in the filename to form a useful archive.

@ryelle is working on a 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/ action to automate the report generation so the details can be worked out within that PR. She added that we will want to move the project over to the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ GitHub in the next few weeks, a prospect which was received with celebration.

@notlaura asked @danfarrow to update #26350 (the !important audit ticketticket Created for both bug reports and feature development on the bug tracker.) with a link to the relevant section of the report and offered a brief roadmap of the next actions: once her config feature is complete we can update the CSS audit ticket and liaise with design to see if they want any additions to the report.

Color Scheming (#49999)

@danfarrow reported still struggling with wp-env and the remainder of the meeting comprised of @ryelle helping him figure out what was going wrong with his setup (thank you!)

As we ran out of time there was no open-floor / link share, so with that the meeting ended. Thanks everybody!

#core-css, #summary