CSS Chat Summary: 22 October 2020

The meeting took place here on Slack. @danfarrow (me!) facilitated, standing in for @notlaura.

Housekeeping

There were no housekeeping items this week.

CSSCSS Cascading Style Sheets. Audit (#49582)

@ryelle reminded us that we have a basic report available on Github. General feedback on the content would be welcome!

@kburgoine posited adding a link to the report to ticketticket Created for both bug reports and feature development on the bug tracker. #26350: !important audit to show some progress on that issue.

@ryelle suggested holding off as the report’s presentation is likely to change soon, and @danfarrow added that, as part of his styling contributions, he’ll be adding in-page links which would allow us to link directly to the !important section of the report.

Color Scheming (#49999)

@ryelle reminded us that she has an environment set up for testing her reduced-colors 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".:

If you’re comfortable setting up a dev environment, you can run this branch; but if you just want to see a demo, you can log into this test site. The username & password are:

username: color-author
password: fPj1ugpm5SMlRR^Evf%zg5)f

(fyi, that’s just an author-level account, and if anything starts getting spammy I’ll reset the password)

There is a dashboard note on the test site showing details of how to contribute.

@ryelle went on to share a Slack post from @helen which clarified an issue which had probably already been lurking at the back of our minds:

Yeah this is unfortunately really hard to judge without (dun dun dun) 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…

We had a brief chat about that particular rabbit hole. @kburgoine mentioned being impressed by percy.io‘s 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/ integration, and @danfarrow mentioned recently enjoying backstop.js.

The discussion concluded with two suggestions:

  1. It would be useful at some point to recap the current landscape of visual regression testing in WordPress in order to judge the feasibility
  2. The colors project could perhaps be put on a back-burner for the time being until 5.6 is released in December and we could focus our attentions on the CSS audit

CSS links share + Open floor

@ryelle posted a call for testing Twenty Twenty-One as a good place for CSS folks to help out, with PRs to review and issues up for grabs. The 5.6 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. would also benefit from your attention – get those issues while they’re hot!

@kburoine shared a link to a very entertaining CSS Tricks article from John Rhea who hand-coded daily CSS animations for 60 days on the theme of zombies.

@danfarrow shared a link to the proposed CSS nesting syntax which would make CSS a bit more SASSy.

Finally @danfarrow concluded the meeting by thanking everybody in #core-css for being so welcoming & supportive since he first attended back in June 2020.

Thanks everybody for attending!

#summary

CSS Chat Summary: 15 October 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

Reminder that @kburgoine will be leading the biweekly 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. scrub next Thursday, October 22, one hour before the CSS Chat meeting.

CSS Audit (#49582)

@ryelle reported her progress of having written up an issue about adding configuration file support to her CSS Audit tool, to which @notlaura reported having been prompted by the issue to begin work on the feature!

The generated reports are now accessible as 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/ pages (here for example). @ryelle observed that eventually this tool should be migrated to the WordPress github repos.

@notlaura mentioned that a comment about report generation should be added to the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., for community reference and put a call out for a volunteer to do this, specifying:

the key items to include in a comment are the link to the generated report (https://ryelle.github.io/css-audit/public/wp-admin) and the next steps, which are to complete the data (missing property values) and to style the template

Color Scheming (#49999)

@ryelle reported that she has kept her reduced-color branch testing site up-to-date with WordPress trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. There followed a short discussion about the pros and cons of proposing to merge 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". into the 5.6 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. @garrett-eclipse suggested seeking a champion from #design, otherwise punting it to 5.7, which, @ryelle observed, would allow us to focus on bug-scrubbing & Twenty Twenty One issues over the coming weeks.

CSS links share + Open floor

@danfarrow (me!) shared a link to a portfolio site ichimnetz.com which has a quirky “adjust CSS” slider feature which demonstrates the effect of using more or less CSS.

@danfarrow also shared an informative recent CSS Tricks article about media queries which includes a reference to a browser feature forced colors mode:

Some browsers will limit the number of available colors that can be used to render styles. This is called “forced colors mode” and, if enabled in the browser settings, the user can choose a limited set of colors to use on a page. As a result, the user is able to define color combinations and contrasts that make content more comfortable to read.

And, with that, the meeting was concluded. Thanks everybody!

#core-css, #summary

Dev Chat Summary 14th October 2020

Hello Friends! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat on Wednesday, October 15th, 2020, 05:00 UTC and Wednesday, October 15th , 2020, 20:00 UTC, following this agenda .

05:00 UTC core dev chat @thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.
20:00 UTC core dev chat @thelmachido facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here.

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/13/dev-chat-agenda-october-14th/

Announcements

  • APAC based core committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., @peterwilsoncc has taken up a role that will allow him to contribute to core 4 days a week 🎉
  • A group is gathering around issues that can be moved to a minor release to clear the path for 5.6 and address issues like removing the embed blocks for FB an Instagram due to their withdrawal of support. If you can help, here’s where to dig in https://core.trac.wordpress.org/tickets/minor @whyisjake will be organizing the release, so reach out if you want to get involved.

No Highlighted Blogblog (versus network, site) posts this week

Updates from Component Maintainers/Focus Leads

Open Floor

  • @mikeschroder observed some failing tests for some hosts and the 0500 UTC crew dug in to find the cause in a package update – resolution to add an issue to the board to be included for the next 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/ release.
  • @isabel_brison threw out that if anyone was keen to work on or review editor-related stuff, the 5.6 project board has a few things to pick up in To do and Needs Review columns :smile:
  • The state of PHP8 support in core generated a fair amount of discussion. Rather than summarize here, please review the archive of the conversation in Slack for all the detail. Major takeaways are the dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are in progress in relation to communication around the significant number of breaking changes – Helen called for a deliberate effort towards outreach of this change which has extensive discussion to follow. Furthermore @omarreiss suggests declaring WP incompatible with PHP8 with a useful perspective from @jrf in response. Lots to dig in there, and there will be marketing and outreach efforts to ensure widespread awareness.
  • @justinahinon opened a discussion with a suggestion regarding pairing existing contributors with new ones to build connection and support newbies.
  • @helen asked for a rundown on significant issues to complete before BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is released,
    • Major Core auto-updates opt-in UIUI User interface
    • Twenty Twenty-One
    • Widgets as Blocks
    • JQuery 3.5x
    • Issues on this list

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 15 2020, 05:00 UTC and Wednesday, October 14, 2020, 20:00 UTC in the #core 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. Please feel free to drop in with any updates or questions.

Thanks to @francina for proofreading this post.

#5-6, #summaries, #summary

CSS Chat Summary: 08 October 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

@notlaura reminded attendees that she will be unavailable on 22 October and needs somebody to step in and run the meeting. If you’re up for it please let her know!

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura reported progress on her PR to add the HTML report to @ryelle‘s super CSS Audit tool which now adds support for a --format=html command line option.

There is a remaining issue with the property-values audit, and contribution is still needed towards improving the design and info formatting.

@notlaura also mentioned an issue she added about the need for property-value audit groupings. A short discussion about possible solutions followed, which gravitated towards adding support for .json config files. @ryelle offered to write up an issue to outline the format she envisages for discussion in 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/.

@notlaura clarified the approaching milestones of merging her PR, updating the tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., and enabling more progress on styling the report which @danfarrow (me!) has started contributing to.

@notlaura pointed out a failing test (Colors › should ignore colors in non-color properties) which @ryelle confirmed she had left as an aide-mémoire for herself to fix the associated issue. @ryelle suggested that this issue might be a good self-contained task for a new contributor to tackle.

Color Scheming (#49999)

@ryelle reminded us of her demo site where people can appraise the reduced-colors testing tool – details in this Slack message. Some issues have already been added to the github repo but wider testing is required.

The plan is to post in #design and #accessibility with info on how to access the tool, how to submit new issues, and prompts to help fix the issues.

@notlaura put out a call for somebody to help with this small task, and offered her assistance to clarify what’s required & to review the message before it’s posted. @ryelle added that she can still write the post if nobody else volunteers (although she had mentioned earlier in the meeting that this month is super busy for her so please consider helping out!)

CSS links share + Open floor

@notlaura shared a link to this CSS-Tricks article about the widening responsibility of front-end developers. @Andrew Joyce added a recommendation for an earlier article by the author on the same theme, The Great Divide.

We reflected about a time when writing CSS involved just writing CSS, and on that poignant note the meeting was closed.

Thanks to everybody who attended!

#core-css, #summary

CSS Chat Summary: 01 October 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

If anybody is interested in being a note-taker for these meetings we would love to have your help!

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura recapped last week’s discussion of her PR to add report generation to @ryelle‘s nifty CSS Audit tool. A git rebase was required for @notlaura‘s PR which she reported is mostly done.

@ryelle reported that the PR is nearly ready to merge. @notlaura sought clarification from @danfarrow (me!) about whether it’s important to have a separate template partial for each section of the report. I was able to (eventually) respond that I believe it is indeed important because the data structure can differ between different report sections.

@ryelle reported having sketched out a promising 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 which would commit the generated report back to the repo, bringing us closer to the goal of automated reports with a version history.

Color Scheming (#49999)

@notlaura recapped last week’s progress where we had design team confirmation of the color list, plus a possible volunteer to help.

@ryelle reported an exciting update – she has set up a demo site on Pantheon for the reduced-colors test. The access details are here in Slack.

@ryelle added that anyone who would like to help or who needs adminadmin (and super admin) access can DM her with their email and she will create an individual admin account for them. She suggested that the wp-core-color-list repo would be a good place to track issues.

@notlaura questioned if we could make it clearer to testers where they can post issues by adding a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to the demo site with some instructions about how to contribute.

@ryelle agreed to add this, but also suggested that it would also be helpful for testers to run 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". under their own setups to get a broader view of compatibility with various plugins, and in particular multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site setups.

There was a short discussion about the value of testing admin schemes at this stage, the outcome of which was “it wouldn’t hurt to check just in case”.

@notlaura pondered the best way to announce this to testers, and suggested notes in #design and #accessibility. @ryelle agreed to add notices to those channels.

CSS link share / Open floor

I (@danfarrow) shared a link to an app I found which is an interactive glossary of CSS vocabulary & terminology http://apps.workflower.fi/vocabs/css/en

It seems like a really useful learning tool, and was received with enthusiasm! There’s also an HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. glossary http://apps.workflower.fi/vocabs/html/en

And with that the meeting was concluded. Thanks everyone!

#core-css, #summary

Dev Chat Summary 8th October 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, October 7th, 2020, 05:00 UTC and Wednesday, October 7th , 2020, 20:00 UTC, following this agenda .

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here .
20:00 UTC core dev chat
@laurora facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here .

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/06/dev-chat-agenda-weds-7th-october-2020/

Announcements

No announcements today!

Highlighted Posts

  • https://make.wordpress.org/core/2020/10/01/whats-next-in-gutenberg-october/ No action needed, but posted for awareness as there are notes for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. or pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party devs and in invite for those interested in contributing.
  • Requests for comments on Starter Content https://make.wordpress.org/core/2020/10/06/revisiting-starter-content-on-org-and-beyond/ – which is a request for comment.
  • Progress update on https://make.wordpress.org/core/2020/10/06/update-wordpress-5-6-release-progress/. No action required though a request for a graphic depiction of what the Full Site Editing simple, routine user flows was discussed. This will help give people a sense of how it’s likely to work when it does come into core as it’s currently hard to visualise something we’ve not seen before.

Updates from Component Maintainers/Focus Leads

  • Build/Test Tools, General: Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support:
    • The PHP 8 Docker image has been updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x
    • A new NPM task has been added to use the Composer-installed version of PHPUnit
    • * There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
    • * Next steps: More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. A call for testing was published earlier this week: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/
      Question was asked: Does PHP8 support need more people involved? A: Follow the issues here PHP8 Tag in trac
  • I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Date/Time, Permalinks: No major news this week.
  • Site Health has had some attention in the past week to go over patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.-refreshes and tickets
  • External Libraries: jQuery update has some progress too #r49101 has updated jQuery and jQuery UIUI User interface. Please test!
  • Upgrade/Install: our main ticketticket Created for both bug reports and feature development on the bug tracker. ( 50907 ) is still in progress.

Open Floor

  • The Marcomms team noted that they’re inviting feedback in relation to the About Page for 5.6 in thisGoogle form feedback is are also welcome via tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. but this form will help make it more accessible to the wider community who might not be familiar with trac and its processes.
  • It was observed that the titles for the dev chat entries in the calendar weren’t updated with the UTC specific timings so @peterwilsoncc updated them to Core Development Weekly Chat (0500 UTC) and Core Development Weekly Chat (2000 UTC)
  • #40351 (Term post re-counts scale poorly, are common and difficult to avoid) – WordPress Trac which is slated for 5.6 has a patch, but the question was asked whether there’s enough time to test properly before adding to the release, after discussion, the plan is for further testing this week, if nothing breaks it will be added to the release.
  • Discussion then went on to explore options for dummy content for testing andthe contingent posted numerous options according to individual preferences to answer the inquirer.
  • #50658 was highlighted for review: ‘has patch. Tested. Has screenshots. Missed wp5.5 deadline and tagged for 5.6. Action: pings sent to the component maintainers for review
  • Ticket https://meta.trac.wordpress.org/ticket/5463 was highlighted for feedback in relation expediting updating process for component and focus teams. Please comment on that ticket if you have feedback.
  • https://core.trac.wordpress.org/ticket/50907 needs more eyes on it and feedback added to the ticket.
  • The Yoast team have put together a short term team to focus on Twenty Twenty-One development, they’ve created a project board which you can follow here to track progress of issues
  • Reminder: next test scrub on Friday October 9th 13:30 UTC
  • Requests for testing: of https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/ and

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 20:00 UTC in the #core 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. Please feel free to drop in with any updates or questions.

Props to @francina for the proofread.

#5-6, #summary

Dev Chat Summary: September 30 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, September 30, 2020, 05:00 UTC and Wednesday, September 30, 2020, 20:00 UTC, following this agenda.

05:00 UTC core dev chat

@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@thelmachido facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.

Both groups followed this agenda: https://make.wordpress.org/core/2020/09/29/dev-chat-agenda-september-30th-2020/

Announcements

@annezazu shared that the navigation screen is being put on pause to focus on Widgets screen as a stronger candidate for 5.6 – there has since been a post added to the core blogblog (versus network, site), which you can read in more detail here the post includes a call out for testers. If you’re available to help you can get details here.

@francina announced that weekly Test Scrubs will be starting this Friday, October 2nd at 13:30 UTC: https://make.wordpress.org/core/2020/09/29/test-scrub-for-wordpress-5-6/

Highlighted Posts

Proposal: A font enqueue API for WP core – Please add any thoughts or comments on the post.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:
@sergeybiryukov shared that work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support has continued. All known unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. issues have been addressed, and the tests are now passing on PHP 8. #50913 includes most of the progress on this, some work was also done in other related tickets: https://core.trac.wordpress.org/query?keywords=~php8

Next steps for PHP 8 support:

  • Docker image needs to be updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x: gdmbstring, etc. There is a PR by @desrosj waiting for review: https://github.com/WordPress/wpdev-docker-images/pull/36. If anyone is able to help with that, please do.
  • There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
  • More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. @andraganescu and @desrosj are working on a call for testing to be published later.

MarComms:
@yvettesonnefeld shared that they have posted the ticket for the About page, with a brief attached. Please add any features that should be highlighted on the About page and release post via a comment on the ticketticket Created for both bug reports and feature development on the bug tracker..

A Google form is being created for those who are struggling to master TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Upgrade/Install:
@audrasjb shared that most of the work is currently focused on Core major versions Auto-updates: #50907

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility):
@sarahricker shared that @jonnyvaughan and Alice Williams are well underway on the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. being developed for #50673. A summary of where they’re at can be found here.

Open Floor

Regarding the Application Passwords Merge Proposal discussed last week, @timothyblynjacobs stated “I think we’ve added the necessary functionality to address the concerns shared in the comments (via filters).”

@janthiel highlighted a small change proposal regarding the quote calculation caching in multisites. The ticket has been around for years now, and implementing it would be a massive performance improvement for sites with huge media libraries and/or slow file systems like NFS using the WordPress Quota system.

@peterwilsoncc wanted to bring attention to #45114. You can read the conversation here. The brief conclusion was to outline 3 options to resolve this (wont fix, move hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., add new hooks) and take a vote. Please add any contributions to the conversation on the trac issue. Comment 27 onwards is a good place to start.

@chanthaboune shared the “sure to ship” items for WP5.6 right now. The struck out items won’t make it to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., based on posts/tickets/comments/feedback/etc. A full post detailing the changes will be published soon.

Ship: Navigation menus blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and screen in Core.
Ship: Automatic updates for major WordPress Core releases (opt-in).
Ship: New features from the block editor upgrades.
Ship: Widgets-editing and CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. support in Core.
Ship: Default theme, including an FSE compatible version.
Ship: PHP 8 support.
Ship: Public beta of Full Site Editing.
Ship: oEmbed changes
Ship: Misc patches/proposals from the community

@azaozz has been going back and forth on the jQuery update to 3.5.1 patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., and would welcome more eyes on: https://github.com/WordPress/wordpress-develop/pull/536, stating that the more difficult part is updating UIUI User interface to 1.12.1 as the build process for that version is completely different. If you have any thoughts, please leave them on the ticket.

WP Accessibility Day is taking place this Friday, October 2nd. More details can be found here: https://wpaccessibilityday.org/

And the week-long WordPress Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day celebrations are currently taking place! Find out more about the full schedule of events here: https://wptranslationday.org/2020-events/

@helen welcomed feedback on whether some round 2 iterative work should be done on Starter Content to get it back to its original intended goal of also enhancing theme previews on 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/. You can see the start of the conversation here, and Helen will be following up with a make/core post.

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 20:00 UTC in the #core 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. Please feel free to drop in with any updates or questions.

#5-5-1#5-5-2#5-6#dev-chat#summary

#5-6, #dev-chat, #summary

CSS Chat Summary: 24 September 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

@notlaura asked for a volunteer to help share the responsibility of writing up meeting notes. @danfarrow (me!) & @ryelle offered to help.

@ryelle cleared up a query from @kburgoine about the /here command in 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/.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported some progress running @ryelle‘s CSS audit tool with @notlaura‘s report generation patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., in order to work on styling the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. output.

@ryelle is merging some of @notlaura‘s updates in smaller chunks, which means the PR needs to be rebased. @notlaura‘s next step will be to complete the rebase so that the audit PR can be merged. Templating updates could then continue in a new PR.

@ryelle hopefully resolved an issue about the property-values audit not running by pointing out that, when specifying which audits to run, the --all flag doesn’t include the property-values audit.

@ryelle has added some tests to the audits for which there was much appreciation.

Color Scheming (#49999)

@ryelle reported some great progress following her post on Make WordPress Design and the subsequent Slack discussion in #design.

The outcome is that we’re using the right color list currently, and we got a volunteer to help check out the updated screens in use.

@ryelle‘s next step is to set up a dev site in order to share the color scheme updates for feedback.

Open floor

@notlaura asked if anyone knew of discussion of color functions being added to CSS. @ryelle posted a link to a w3c working draft for implementing a color-adjust function which includes possible solutions including color-contrast, color-mix, brightness() and relative color syntax

Thanks to everybody who attended this week!

#core-css, #summary

Dev Chat Summary – 23 August 2020

Greetings! Here’s what happened in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Wednesday, September 23, 2020, 07:00 AM GMT+2 and Wednesday, September 23, 2020, 10:00 PM GMT+2 on the #agenda.

0500 core devchat

@thewebprincess led the discussion in the meeting was a bit slow the team decided to run 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. scrub. Find the full Slack archive here.

2000 core devchat

@laurora facilitated the chat and @thelmachido took notes. Find the Full Slack archive here.

Announcements

To see an overview of what’s happening keep an eye on make/updates, we’ve got quarterly updates from the team coming soon.

Highlighted blogblog (versus network, site) posts

Dual licensing Gutenberg under GPL v2.0 and MPL v2.0
We need to gather feedback on the proposal to dual-license 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/ under GNU General Public License, v2 (GPLGPL GNU General Public License. Also see copyright license. v2) and the Mozilla Public License v2.0 (MPL v2.0). Please share your perspective on the proposal from Maxime by adding comments to the post.

Introducing the next WordPress default theme – Twenty Twenty One Weekly meetings on the theme will start on Monday 28 September at 15:00 in #core-themes. @chanthaboune clarified that the team will be shipping one theme, based on Seedlet, bundled with the release and they will be exploring a second FSE theme, after the first is stable, that is not bundled with the release. Besides what was discussed in 5.6 planning post, FSE will now be done in the Gutenberg PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party as a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. feature. See what the team said in the full slack discussion and another on-going discussion is going to be opened on make/core.

Proposal on REST API Authentication / Application Passwords
George Stephanis has put together a proposal for this, the hoped timeline for this proposal is version 5.6 but the team is not yet certain. There have been attempts to get other authentication mechanisms to a considerable state but none have been proposed for core as yet. See what the team contributed to the discussion in 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/.. The discussion from here on out will be on #core-passwords even though they had temporarily been in #core-restapi. Feel free to join the discussion there.

How gather updates from component maintainers & focus leads
Go through the post and share your opinion on the best way to gather updates as we are getting closer to release. Please share your perspective by commenting on the post by Wednesday 30 September.

Facebook embeds being deprecated
How will cached embed look after the deprecation date?. There is need to test and collect data on how the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. scripts included in the embed will look after deprecation. How will the marketing crew share this information and more broadly with users as a whole?. These are some of the discussions that will be wrapped up in the comment section of the post.

Component maintainers

Build/Test Tools
Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support. With quite a few fixes to unit tests and some fixes to core, this brings the tests from 87 errors and 331 failures on PHP 8 a couple of weeks ago (when the work has just started) to only 5 errors and 17 failures now (still to be addressed). Ticketticket Created for both bug reports and feature development on the bug tracker. #50913 includes most of the progress on this, some work was also done in other related tickets here.

For I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. component one change was committed this week. The Default Language networknetwork (versus site, blog) option in Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site now has a language icon next to it. View ticket #51359.

Menus & Widgets have a couple of tickets that are waiting for committers to have a look at them.

Upgrades & Install the first patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for Major Core auto-updates ticket has been added, also there are a couple of tickets that are waiting for committers to have a look at them.

Additional eyes needed on testing and review for backlog on the Privacy component.

No updates of note this week from Date/Time, Permalinks or Site Health.

Open Floor

@ramiy put together a Post & Infographic on WordPress release facts & stats.

@enricocarraro is working towards making WordPress Strict CSP-compatible. Inline scripts refactoring #39941 and Inline event handlers and JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. URIs refactoring #32067. If anyone could review his PR that would be greatly appreciated.

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 30, 2020, 07:00 AM GMT+2 and Wednesday, September 30, 2020, 20:00 PM GMT+2 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-5-1, #5-5-2, #5-6, #dev-chat, #summary

CSS Chat Summary: 17 September 2020

Housekeeping

Reminder that next week will be 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. scrub, this time led by @kburgoine and starting at 4pm EDT on Sept. 24 (one hour before the weekly chat). The bug scrubs (a.k.a. triages) are a great way for new contributors to get involved!

CSS Audit (#49582)

I’ve been working on a 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". that displays the audit data in 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/ pages. The initial version can be seen here and the work in progress pull request is here. The next steps for the PR are getting documentation in place about generating reports, and styling the template.

More important, as @ibdz noticed – it looks like the audit for properties and values is not running, so we definitely need to get the data for about font-sizes and pixel usage into the report.

Color Scheming (#49999)

@ryelle drafted a post to for Make design about the color replacements work so far, specifically to ask what color list we should use, and to start gather folks who would be interested in testing the replacements once a list has been decided on.

Open floor + CSS link share

I shared a link about the ::marker pseudo-element that allows us to style list bullets with CSS. It does not have full browser support yet, but is definitely a feature that can be used with @supports feature queries.

Thanks to @CodeXplorer and @ibdz for being enthusiastic first time attendees!

#core-css, #summary