CSS Chat Summary: 29 October 2020

Full meeting transcript here on slack. @notlaura facilitated the meeting & @danfarrow wrote up this summary.

Housekeeping

@notlaura reminded everybody to complete the WordPress 2020 survey – it takes less than 10 minutes so if you haven’t already done so, you know what to do!

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura reported nearing completion of her PR to add config file functionality to the audit tool, as discussed in previous meetings.

@notlaura agreed with last week’s conclusion that the audit report needs a little refinement before being shared on the !important audit ticketticket Created for both bug reports and feature development on the bug tracker., #26350. @sabernhardt consequently offered to update that ticket’s milestone to 5.7, which was welcomed.

Color Scheming (#49999)

@notlaura contributed some valuable insights to last week’s discussion (which she had been unable to attend) about 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 being a potential stumbling 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. for #49999.

She clarified that visual regression testing had been discussed right at the start of the CSS Audit project, back in March, and drew our attention to a ticket opened by @isabel_brison #49606 Add visual regression testing to core.

@isabel_brison also submitted a PR to integrates visual regression testing into e2e coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tests, using jest-image-snapshot. In the most recent comment however she concluded that visual regression testing might be better implemented as a separate script to be run locally, rather than part of the e2e core test suite.

Back in the meeting, @notlaura suggested that checking out this PR might be a good starting point to continue exploring the subject. @danfarrow (me!) offered to look into this, despite not really knowing what’s involved. Only time will tell if his eagerness to contribute is misplaced!

@notlaura suggested adding a new agenda item for visual regression testing, to which @danfarrow agreed.

Further to last week’s discussion, @notlaura agreed that seeking feedback on the color scheming tests should be deprioritised until the release of 5.6.

CSS links share + Open floor

@danfarrow shared a link to a processor intensive (in Firefox at least – it’s not so bad in Chromium) CSS only puzzle game where the goal is to click blocks in order to build a lighthouse before night falls.

@notlaura shared a link to an MDN page about CSS Logical Properties and Values.

CSS Logical Properties and Values is a module of CSS introducing logical properties and values that provide the ability to control layout through logical, rather than physical, direction and dimension mappings.

This module introduces many new properties and values into CSS which may soon be encountered in the wild, so it’s good to get a heads-up on what they’re all about.

And with that the meeting was concluded. Thanks all!

#core-css, #summary

WordPress 5.5.3 Release – Some Technical Details

Today WordPress 5.5.3 was released, the day following WordPress 5.5.2.

It is suboptimal to have releases this quickly in succession, but the details below hopefully describe a scenario that you will agree was worth resolving as quickly and safely as possible.

5.5.2 and ZIP installs

An error with one of the fixes made in WordPress 5.5.2 caused an issue with installing ZIP packages available 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/ for new versions of 5.5.x, 5.4.x, 5.3.x, 5.2.x, and 5.1.x. The issue only affected fresh WordPress installations without an existing wp-config.php file in place.

During the release process for 5.5.2, the package testing workflow returned a false positive, so this issue was not caught. This is a difficult issue to test for, but the first steps are to update the existing documentation so future release teams can learn from this experience. Additional research will be required to find a long-term solution. Updates on this progress will be shared in future Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. posts.

To fix this issue, the Core team released WordPress 5.5.3. It provides a clean ZIP package for the WordPress.org download page for the 5.5.x, 5.4.x, 5.3.x, 5.2.x, and 5.1.x versions.

Resolution of 5.5.3-alpha

While work was being done to prepare for WordPress 5.5.3, the release team attempted to make 5.5.2 unavailable for download on WordPress.org to limit the spread of the issue noted in the section above, as the error only affected fresh installations. This action resulted in some installations being updated to a pre-release “5.5.3-alpha” version (see more here). The appearance of a 5.5.3-alpha version is now resolved with the help of the Systems team.

WordPress 5.5.3-alpha has no functional differences to the 5.5.2 release. To correct this version on your site, you can either click the “re-install WordPress” button on the Dashboard → Updates screen or update to 5.5.3.

Props to @jeffpaul for drafting this post, and to @chanthaboune, @cbringmann, @audrasjb, @davidbaumwald, and @hellofromtonya for editing.

#5-5-3

Media Meeting Recap – October 29, 2020

The following is a summary of the weekly media component meeting that occurred on Thursday, October 29, 2020 at 14:00 UTC. Weekly media meetings are now held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @sageshilling, @florian-tiar, @hongnizzle, @johnbillion 

Upcoming Meeting Schedule

The team discussed moving the regular meeting time to adjust for daylight savings time. It was agreed moving forward, the meeting will be taking place on Thursdays 15:00 UTC time as opposed to the current 14:00 UTC time. 

5.6 Remaining Tickets

#50972media_handle_sideload() does not allow $post_data to override – Currently owned by @sergey and set to reviewing, this ticketticket Created for both bug reports and feature development on the bug tracker. needs unit tests at the moment. @johnbillion mentioned that the functions aren’t very testable without refactoring, so the group agreed this ticket is a candidate to move to 5.7.

#41648Alignment issue on media-new.php when browse uploader screen is activePatchpatch 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. is ready to go and @antpb will review and commit. 

#39968Media Library deleting all items on the last page loses pagination/navigation buttons – This has been addressed by @florian-tiar and is ready for review. It was agreed that this was related to existing changes in 5.6 so it is safe to test and commit before the next 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. cycle.

#51396[Media upload.php] Switch back from grid to list mode reopen the modal. – This is a quick fix for an existing 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.. @florian-tiar mentioned that this is not a critical bug so please chime in in the comments below if you have any thoughts on this fix being implemented in 5.6 or if it should wait for 5.7.

Props @antpb for proofreading and final review.

#media, #summary

CSS Chat Agenda: 29 October 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, October 29, at 5:00 PM EDT.

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) – Config and template styles
    • Color Scheming (#49999) – 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
  • Open floor + CSS link share

#agenda, #core-css

Dev Chat Summary – 28 October 2020

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack

Both groups followed the pre-prepared agenda and started the chat by celebrating the release of WordPress 5.6 Beta 2, please test and review the 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. version and share any bugs/issues.

Announcements

WP Version 5.5.2 is scheduled for release on October 29th

Highlighted Posts

@helen is running code review/commit office hours for 5.6, you can get more information about it here.

@chanthaboune outlined the rationale behind dropping the Widgets screen from 5.6 catch up on that and the plan going forward here.

Dark Mode for Twenty Twenty-One
Discussions are ongoing and the team has outlined some options that your input could help narrow down.

Calls for maintainers and focus leads

PHP 8 call for testing
@sergeybiryukov highlighted again that there is need for more testing on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8, we have to expand test coverage and creat tickets for any issues found. A thorough report has been written by @omarreiss, @jrff, and @herregroen about the current state of PHP 8 and its compatibility with WP.

Build/Test Tools
Docker environment was updated to allow for using multiple PHP Unit versions, get more details on that here. (Note: this is currently temporarily reverted to investigate test failures) Also, some changes were made to account for the recently released Composer 2.0.

Upgrade/Install Component Update
@audrasjb is drafting on a dev notedev 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. for #50907. It should be ready for review by the Docs lead/cohort/mentor.

Open Floor

Take part in the 2020 WP English Survey, if you are interested to see 2019 survey results, or get links to the 2020 survey in French, German, Japanese, Russian, or Spanish, you can find all that here!

Block Pattern Directory Ideas and Discussion
@daisyo surfaced the post for feedback.

@audrasjb is working on a technical proposal for dropping support/security backports for very old versions of WordPress. He is going to publish a Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post and open a ticketticket Created for both bug reports and feature development on the bug tracker. with a 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. proposal very soon. The topic should be ready for discussion during the next dev chat. Comments are welcome here. Follow the conversation on slack

Join the team for the next bug scrub on Friday

WP 5.6 Beta 3 is Scheduled for next Monday.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 4, 2020, 07:00 AM GMT+2 and Wednesday, November 4, 2020, 10:00 PM GMT+2 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. 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, #5-5-1, #core, #dev-chat, #summary

Editor chat summary: 28 October, 2020

This post summarizes the latest weekly Editor meeting (agendaslack transcript). This meeting was held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor 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 on 2020-10-28 14:00 UTC and was moderated by @annezazu.

Announcements

  • Gutenberg 9.2.2 was released on October 26th.
  • WordPress 5.6 Beta 2 was released on October 27th! Please install on a test site, play around, try to break everything, report bugs, and all that good stuff: 
  • WordPress 5.5.2 is coming to your WordPress site on October 29th.

Monthly Plan & Key Project Check-in

For context, here’s the overarching plan for October.

Widgets Screen Update shared by @andraganescu

The focus for the people previously working on this screen is now mostly on 5.6 efforts. However, there still is work around advancing various widgets project related issues. For example, @zieladam‘s PR about fixing concurrency related issues, something which became apparent while working on the widgets editor.

Reminder: the 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. core sync chat is suspended until 5.6 has been released!

Global Styles Update shared by @nosolosw

Global styles has advanced nicely this month with @jorgefilipecosta doing great work related to user-provided color palettes, etc. We’re now going to have a stronger focus on tighten things up to work great with the TwentyTwentyOne 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. based theme. Some of the items in the first wave of work will also be moved to the “future” iteration at this point.

Full Site Editing Update shared by @vindl

Full Site Editing – Navigation update:

  • Search feature for the navigation component has been merged. The next step is integrating it with the site editor.
  • It’s now possible to create new templates from the navigation sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. that correspond to default ones from template hierarchy.
  • We shipped the RTL support for the navigation component.
  • PR for creating template parts from multiple blocks selection has been merged.
  • There is a proposed framework PR for introducing a custom status for templates provided by themes (or plugins) as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. files, which haven’t been customized by the user yet.

In other news:

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.  Remember: don’t just focus on code contributions!

@nosolosw

Mainly focused on fixing issues raised in 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 and will continue to help with that, but will also come back at global styles work.

@aaroncampbell

Was trying to verify whether Single Column Functionality, which looks like it made it into 9.2, is going into WP 5.6. As a result, this small screen display issue was put in the 5.6 must-have project board to be triaged.

@annezazu

Wrangled some quicker doc updates: glossary terms to include more block based items, triage instructions to include tables for clarity & reasons for closing, and updated the Versions in WordPress doc for 5.6 (need to do the same for 5.5.2). Outside of that, helped clear out a bit of a backlog for unlabeled items, did some FSE testing/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. reporting, and started gathering resources for the contributor working group effort!

@youknowriad

Starting to work on more FSE tasks: trying to streamline the flows to enable/disable FSE themes. Still working on documentation for 5.6 new APIs and 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.. Hoping to have time to chime in on this thread soon.

@mkaz

Has been working on improving e2e tests.

Open Floor

Should we bail on e2e tests after a single failure? Raised by @mkaz.

Marcus has been working on trying to improve tests and asked the group for thoughts on whether we should bail on e2e tests after a single failure as it’s not clear if there’s value in doing so. This is particularly the case for 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/ Actions to keep running all the tests after an error happens. After a quick discussion with people sharing their differing approaches to handling failures, @youknowriad summed up the root issue nicely: “I feel the issue is not that we run the whole suite on github but more that the tests actually fail…What we should do is actually take the time to fix the failures even if we’re not responsible for them”.

What should be included in the next “What’s Next” in 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/ post? Raised by @daisyolsen.

@nosolosw made sure to link to the previous update around Global Styles. @youknowriad mentioned both that writing Dev Notes should be mentioned for preparing for 5.6 and that he personally would like to see a greater focus on FSE related work.

Is the current plan to use PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 files instead of static HTML files for FSE? Raised by @johnstonphilip.

@youknowriad once more swooped in to share that there’s an exploration along those lines being done here.

#core-editor #core-editor-summary

Dev Chat Agenda: October 28th 2020:

Here is the #agenda for this week’s meetings happening at:
Wednesday, 28 October 2020, 0500UTC and Wednesday, 28 October 2020, 2000UTC .

  • Announcements –
    • 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. 2 of 5.6 released – please test and review and bring any issues/bugs to chat to discuss
    • WP 5.5.2 minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. planned for Thursday, 29 October 2020 1700UTC details here
  • Highlighted blogblog (versus network, site) posts
  • Calls from component maintainers and/or focus leads
  • Open Floor
    If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 28 October 2020, 05:00UTC and Wednesday, 28 October 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#5-6, #agenda

Editor chat summary: Wednesday, 21 October 2020

This post summarizes the weekly editor chat meeting on Wednesday, 21 October 2020, 14:00 UTC held in Slack.

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/ 9.2 and WordPress 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. 1

@jorgefilipecosta announced Gutenberb 9.2 was released some hours before: https://make.wordpress.org/core/2020/10/21/whats-new-in-gutenberg-21-october/.

Regarding WordPress 5.6 Beta it was released on the previous day as planned: https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/.

Unfortunately the 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. Blocks were not part of the WordPress release. More context is available at https://core.trac.wordpress.org/ticket/51506#comment:13.

@jorgefilipecosta referred that there is a must-have board that contains the issues that should be addressed before the next WordPress release https://github.com/WordPress/gutenberg/projects/48. Some of these issues are not yet assigned to anyone so it is a good opportunity for someone looking to contribute and have an impact on the next WordPress release.

Monthly plan updates

Full Site Editing – Navigation – @vindl

  • Pages selector dropdown has been removed in #25620. This functionality is now accessible through the navigation sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., similar to templates.
  • The initial version of Document Settings dropdown in site editor has been completed. It contains basic template info and a button to view all templates.
  • Work is in progress for adding new functionality to the navigation sidebar, most notably the search featuretemplate creation flow, and RTL support.
  • Hover interaction for template parts is on hold after latest round of design feedback and will have to be reworked or abandoned.
  • Old PR for converting blocks selection to template part has been picked up again and updated.

Full Site Editing – Navigation – @ntsekouras

  • The Add sticky support in Query 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. (https://github.com/WordPress/gutenberg/pull/26279) a needs review.
  • Query block enhancements(loading and no results messages, focus Query on insertion)

Global Styles – @jorgefilipecosta

Widgets Screen – @zieladam

  • We are regrouping on #feature-widgets-block-editor to figure out what’s next – anyone interested in this project is welcome to join.
  • Widgets-related work had some positive effects such as widgets APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoints or bringing in support for batch requests in WordPress (props especially to @timothybjacobs and @Jonny Harris).

Task coordination

@jasmussen

Submitted the following PR’s:

@annezazu

Shipped the Block Editor Release Process for Major Releases with major props to our host @jorgefilipecosta and @tellthemachines, reported 13 Widgets Screen related issues to 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/, and lots of additional testing including with the latest for FSE.

@ajlende

  • Woking on a new image-related feature: duotone filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. support #26361.
  • Some of the menu stuff is blocked by #26115 (which @ajlende is currently working on).
  • Cover block support is blocked by #25171.

@mapk

  • Query block
    • Introducing placeholder screen.
    • Creating a new post from block.
    • Swap out patterns for block.
  • Widgets screen
    • Going through feedback and helping with design related issues.

@youknowriad

  • Tried to help a bit with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. package updates and patches for 5.6.
  • Started working on documentation for the new APIs in 5.6.
  • Doing some prototyping related to FSE.
  • Helped a bit with e2e tests (please help there if you have time, we’re not on a great stop at the moment).

@zieladam

@mcsf

  • Focused a lot on rethinking our Block Supports implementation, starting with 26111, then discussing details with @youknowriad and @nosolosw in 26192 and follow-up PRs
  • PR reviews in general

@ntsekouras

  • Add sticky support in Query block(https://github.com/WordPress/gutenberg/pull/26279) – needs review
  • Query block enhancements(loading and no results messages, focus Query on insertion)
  • Recognize and convert old or derivative block types to their canonical form(https://github.com/WordPress/gutenberg/pull/26147)
  • 5.6 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. fixes

@jorgefilipecosta

  • Proposed a PR to generate preset classes on the client-side https://github.com/WordPress/gutenberg/pull/26224.
  • Proposed a PR to use the block settings on the global styles block panel instead of the global ones https://github.com/WordPress/gutenberg/pull/26319.
  • Merged the pass of dynamic editor settings to the block editor on the edit site screen.
  • Iterated and merged the video text tracks functionality.
  • Iterated and merged the columns and group block templateLock control functionality.
  • Fixed a timezone issue that was considered critical and will be backported for older versions. Did an audit to the way we format dates on the frontend and suggested a general fix (we still have issues currently when we use formats with a complete timestamp like ‘c’ used for time HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. elements)
  • Did some PR reviews.

For the next week, will see how we can proceed regarding date-time, review the related PRs, etc. Will improve the font size presets (having global styles rely on pixel values for font sizes exclusively is not a good idea). See what can be done regarding identifying if a block instance matches a global style selector (for cases like headings). Will continue the iterations on the PR’s that are open and do some PR reviews.

@vcanales

  • PR for moving away from momentjs and into date-fns: https://github.com/WordPress/gutenberg/pull/25782 — Needs review, all input appreciated — Most tests passing, and @vcanales is currently testing and trying to fix this issue related to post schedule date mismatch, with the library swapped out.

@frankklein

Got two FSE bug fix PRs open:

  • Template part generation fix (i.e. do not use text domain): https://github.com/WordPress/gutenberg/pull/26275 already reviewed, and ready for merge.
  • Fix theme exports (these don’t work at all at the moment) https://github.com/WordPress/gutenberg/pull/26268

@nosolosw

His focus has been lately on various things that were important to land on 5.6. Plans to get back to FSE/GS work this week.

@bph

Testing daily builds of the plugin.zip (for now published on Gutenberg Times).

@karmatosed

Now options iterations are in 5.6, moving to beyond those for next releases. Also shepherding 5.6 and picking up some little pieces along way.

@itsjonq

  • Continued with G2 Components explorations, with a focus on supporting Design Tools (starting with Typography)
  • Building in features like CSS validation and smarter unit parsing (e.g. px, or vmax) to expand Gutenberg’s abilities to handle custom values (as Global Styles evolves)
  • Continued knowledge sharing of all sorts (G2, design, UIUI User interface, dev) via Zoom sessions

Open floor

Updating 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. editor more frequently

@clorith said:

Continuous Gutenberg releases in trunk.Currently, changes to 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 generally get merged to core a few days before beta-1 of a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. going out.

In that time period, months have likely to have passed, and the plugin would have had multiple releases (taking the 5.5 as an example, 9 releases of Gutenberg were bundled, the same rungs true of WP 5.4, 10 releases made it into 5.3). That’s a lot of changes, not all of them obvious, but having all of them land right before beta makes it harder to test their interaction purely in core, and separate between experimental plugin stuff, and what is actually planned for core.I would like to see a continuous integration between the two projects, I’ve outlined a proposed running timeline to get the discussion started around this:- Plugin has a new version releases

– The changes live in the plugin for 3 weeks

– After these 3 weeks the changes are merged to trunk

– Feedback on trunk/core can be provided on the features on how they work without all the other bells and whistles of the plugin.I chose the arbitrary number of 3 weeks, as that gives ample time to get plugin feedback from those using the plugin for testing, while also not keeping changes away from core for “too long”, and also doesn’t lead to excessive extra work for committers tasked with Gutenberg chores (ideally, I’d love a 2 week turnover, as I feel that gives ample time for plugin feedback, but this is what we’re here to discuss 🙂 )

@youknowriad said that our official plan is to actually merge after each release with trunk. The only blockerblocker A bug which is so severe that it blocks a release. is that  we don’t  have the resources to do so. And added that the part that can be automated is already automated: updating the packages and the e2e tests against core. The rest (PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 changes) can’t be automated.

Multi-line Code blocks 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.

@getdave said:

There is a regression in the latest Gutenberg release on the Code block (and possibly also the Classic Block) where formatting is completely broken.

https://github.com/WordPress/gutenberg/issues/26301

It looks like this was introduced by changing from PlainText to the RichText component. All the link breaks are now returned as br tags which causes everything to render on a single line.

My personal website for example now shows all my code snippets in one unformatted long line which isn’t great (at all).

Not sure how complex this is to fix, but should we look to address it as a high(ish) priority?

@jorgefilipecosta said he thinks @ellatrix  is already aware of this issue and looking into a solution.

Should we have an issue per PR?

@paaljoachim said:

It seems fairly easy today to create a PR and have someone review and have it merged without even someone from design or 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) have gone through the PR. The question that comes up… should all PRs have an associated issue?

As it seems an issue will have greater visibility and it is easier I believe for someone to add the correct labels to get it looked at.

@jorgefilipecosta and @youknowriad manifested their thoughts against the idea of forcing an issue per PR.

It seems the biggest issue is having PR’s without labels that don’t get the deserved attention, and we should all make sure our PR’s are properly labelled. In case you have PR’s open please verify if all of them include labels.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting-notes

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

Widgets Screen Not Shipping in 5.6

The Widgets Screen project was pencilled in for 5.6, but as of 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, work on its major features was not complete, so Release LeadRelease Lead The community member ultimately responsible for the Release. @chanthaboune, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead @helen, Editor Tech Lead @isabel_brison and some of the contributors working actively on the project — @noisysocks, @talldan and @kevin940726 — decided to exclude it from 5.6. Thank you to everyone who tested and gave feedback as it helped inform this decision! 

The Reasoning

Making the Customizer work with the block editor is a challenging process, and one that needs  substantial and thoughtful work to make sure that we deliver the best possible user experience. At the current stage of this project a bulk of that work is done, but more focused testing revealed notable concerns for overall usability (including 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. interactions, some confusions between 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. & legacy widgets, and UXUX User experience disparities between the old and new screens). You can read more in the ticket.

Next Steps

We will continue working on the Widgets screen, and will keep the new screen as the default option when using the 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/ 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 to encourage more feedback.  At the top of the year, we’ll explore where this fits in the larger roadmap for future releases. For those looking to get involved until then, check out the options below: 

  • It’s been tentatively added to the WP5.7 milestone, with an early tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) so that it comes up in scrubs as quickly as possible.
  • If you’re interested in following the status of the project, you can find the top priority issues and current focuses on the Widgets Editor project board in GitHub
  • If you can help with development, we encourage you to attend or review the weekly triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions in the #core Slack channel on Wednesdays at 7am UTC.
  • If you can help with testing, please feel free to leave comments on the Call for Testing for us to review or to open issues directly in GitHub. In particular, we’d love to hear from plugin and theme authors. 

Thanks in advance for everyone’s help making sure that this key element is a success!

#5-6, #5-7