CSS Chat Summary: 19 November 2020

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

Housekeeping

@kburgoine made a proposal that the 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. scrubs could target tickets other than those specifically related to the next release, in order to give them some needed attention & to keep things interesting for the scrub attendees.

@notlaura suggested a 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/-specific scrub which @ryelle & @kburgoine seconded. @ryelle also suggested focusing on awaiting review tickets.

CSS Audit (#49582)

@notlaura is working on some improvements in the config PR per @ryelle’s feedback. @danfarrow has started to make sense of the twig templating hierarchy, and has made progress on the styling side of things.

The next step is for @danfarrow to submit a PR to be merged with the UIUI User interface updates. We can then add a direct link to the !important audit section into the related ticketticket Created for both bug reports and feature development on the bug tracker. (#26350) as previously discussed.

Both @notlaura & @danfarrow are hoping to have more progress ready to share at next week’s meeting.

Color Scheming (#49999)

There was no progress to report here but @danfarrow is ready to run the 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. tool on the updated adminadmin (and super admin) colour scheme prior to next week’s meeting.

CSS links share + open floor

@danfarrow has improved his confidence with flexbox by playing the Flexbox Zombies game he mentioned last week. @notlaura mentioned CSS Grid Garden, a similar game for mastering grid.

@danfarrow also mentioned Service Workies, a game by the same author for learning about Service Workers.

Related to this, @notlaura mentioned wanting to read Jeremy Keith’s book Going Offline.

And with that the meeting itself went offline. Thanks everybody!

#core-css, #summary

Dev Chat Summary: November 18 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, November 18, 2020, 05:00 UTC and Wednesday, November 4, 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/11/04/dev-chat-agenda-october-4th-november-2020/

Announcements

RC1 of 5.6 has been released! The team would love you to help by testing the release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)., and/or by offering any translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. skills. More information can be found in the Release Candidate post.

@helen shared that the theme previewer site [wp-themes.com] is now showing starter content for the demos for Twenty Twenty One, Twenty Twenty, and Twenty Seventeen, thanks to some help from @dinhtungdu and @dd32. Helen noted that it is not yet available for themes at large; the reasons for which she’ll be sharing in a post that’ll be published soon.

Highlighted Posts

A Week in Core – November 16, 2020

Site Health Check changes in 5.6

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 starting to show up ready for final release, here’s the latest dev-notes 5.6

Updates from Component Maintainers/Focus Leads

General:
@sergeybiryukov shared that PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 release is scheduled for November 26. For WordPress 5.6, the current plan is to declare it as “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. compatible with PHP 8”. A post on make/core is coming soon, but you can see the reasoning behind this in the following 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/. conversations:
https://wordpress.slack.com/archives/C02RQBWTW/p1605646136362600
https://wordpress.slack.com/archives/C02RQBWTW/p1605646630372100

@desrosj added that the 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 this is almost complete, and will be added tomorrow [November 19].

Open Floor

@isabel_brison flagged that there are still a number of outstanding issues in relation to the editor. If you think you might be able to help out in clearing these, please take a look at the to-do column on the Gutenberg project board on GitHub.

@webcommsat shared that the Marketing Team is working on questions and answers for 5.6 for the HelpHub and working with the Training Team. The team will add the latest version to the Marketing Team GitHub at the end of this week, for those who are interested in helping with this.

@desrosj apologized for the delay in publishing the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. – this will be published by the end of the week.

@francina has started recapping the comments to the post about aligning the WP release cycle to industry standards. Right now there are very few voices, and despite the deadline for feedback stated has now passed, she would still love to hear from more people. Please review the post and share your feedback.

@whyisjake asked when the planning for the 5.7 release cycle (team etc) is going to start. @francina suspects @chanthaboune has a plan, but stressed that it would be great to see 5.6 squad members back again, and encourages anyone who has any questions about being part of the release squad to reach out to her or @audrasjb. Francesca will be adding a list of release squad roles and more information on how you can get involved in the handbook soon.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 25, 2020, 05:00 UTC and Wednesday, November 25, 2020, 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions.

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

CSS Chat Summary: 12 November 2020

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

Housekeeping

We discussed the timing of the 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 and that we will shift it to one hour later to stay with the usual one hour before the weekly meeting.

@sabernhardt will also help lead bug scrubs, and can rotate in with @ryelle and @kburgoine. @kburgoine will be leading the bug scrub next week (which is today…I am writing these notes quite late 🤭)

Updates

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura made progress on a pull request to the css-audit repo to support storing audit configuration in a file. @danfarrow said he has pulled the latest version down and is getting back up to speed with styling the report, and intends to do a different template per report type.

The next step for the CSS audit it to get a review on the config pull request above, and to continue work on the report styling.

Color Scheming (#49999)

There were no color scheming updates this week as are paused on asking for feedback until after 5.6 is released.

That said, the WP Adminadmin (and super admin) can be tested with the color replacements using the login info outlined in this Slack message.

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

@danfarrow said he has gotten the tests running locally.

The next step will be to test the reference screenshots against this pull request that contains the color scheme replacements.

Open Floor + CSS Link Share

No open floor topics this week, but a couple of quality link shares!

@notlaura shared The Raven Technique for CSS-only container queries.

@danfarrow shared that the classic Flexbox Zombies game has gotten a nice update – it’s a great way for folks to learn the concepts of flexbox.

#core-css, #summary

Dev Chat Summary: November 11 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 November 11, 2020 at 0500 UTC and November 11, 2020 at 2000 UTC, following this agenda.

05:00 UTC core dev chat

@peterwilsoncc facilitated the meeting and @mikeschroder 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.

Announcements

The WP 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. 4 has been delayed and will now be released around November 12, 2020 at 2000 UTC.

Highlighted Posts

And recent posts on the Make/Core blogblog (versus network, site) to highlight are:

Updates from Component Maintainers/Focus Leads

General: PHP8 is scheduled for November 26th, please see the PHP 8 call for testing to ensure we are ready before RC 1 scheduled for launch on November 17th. @desrosj is working on 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..

Site Health: Most remaining patches complete for 5.6. Dev notes remaining.

Open Floor

@mikeschroder asked for help with getting PHP8 working with the automated hosting tests, as it’d be great to have hosts running the core tests with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 before 5.6 is released. Logs from that discussion found here.

@joostdevalk sparked a lively discussion with the following statement “If we enable auto-updates for core, we should default to it for all plugins too.” It is worth reviewing the conversation.

Finally, @helen put the call out for people to leave their thoughts/comments regarding Dark Mode in Twenty Twenty-One on the recent post.

Next Dev Chat meetings

The next meetings will take place on November 18, 2020 at 0500 UTC and November 18, 2020 at 2000 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 @thewebprincess helping to compile these notes, @hellofromtonya for proofing, and @davidbaumwald for final review.

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

Media Meeting Recap – November 12, 2020

The following is a summary of the weekly media component meeting that occurred on Thursday, November 5, 2020 at 15:00 UTC. Weekly media meetings are 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, @johnbillion, @paaljoachim, @hellofromtonya, @mista-flo, @hongnizzle

5.6 Remaining Tickets

@mista-flo mentioned two tickets that were not included in the 5.6 milestone but should have. These have been committed as of today.

#39968Media Library: deleting all items on the last page loses the pagination/navigation buttons and shows message – The ticketticket Created for both bug reports and feature development on the bug tracker. is related to existing changes in 5.6 and wasn’t added to the milestone. This has been reviewed and committed.

#51396[Media upload.php] Switch back from grid to list mode reopen the modal – Consensus from those present in the media meeting was that this was a safe change to include in the 5.6 milestone. It has since been committed.

Because there wasn’t time to complete the agenda item to review new tickets that require attention, @antpb is proposing 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 away from the regular meeting times. The list has grown quite a bit, so any assistance is appreciated! Please leave a comment below with a time that works for you.

Props @antpb for proofreading and final review.

#core, #media, #summary

CSS Chat Summary: 5 November 2020

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

Housekeeping

Daylight savings time caused a bit of confusion this week, and we decided to keep the meeting at 5pm EDT and 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 one hour earlier every other week (the next bug scrub will be November 19th).

CSSCSS Cascading Style Sheets. Audit (#49582)

No CSS audit updates this week – work is still being done on adding the option for a config file to the css-audit repo (PR here) and adding some template style to make the results more readable.

Color Scheming (#49999)

There were no color scheming updates this week – we discussed putting a pause on asking for feedback until after 5.6 is released. That said, the WP Adminadmin (and super admin) can be tested with the color replacements using the login info outlined in this Slack message.

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

@isabel_brison did some experimenting for on visual regression testing a while back, and mentioned that the setup worked locally, but what quite brittle and ran into problems on CI. @danfarrow tried out running the tests recently from this pull request. @isabel_brison suggested the best approach for running the tests on CI would be to:

  • generate snapshots from the main 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".
  • switch to the feature branch and run the tests for the comparison

This would be as opposed to storing the local snapshots in the repo because there are always different pixel differences depending on the machine where the screenshots were taken. This approach would also solve the issue of storage space in the repo.

Open Floor + CSS Link Share

@ravipatel asked a question about ticketticket Created for both bug reports and feature development on the bug tracker. #51706 which had some browser compatibility issues.

@sabernhardt asked for help testing theme editor styles in #51157, and to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” him in the channel if any questions.

#core-css, #summary

Media Meeting Recap – November 5, 2020

The following is a summary of the weekly media component meeting that occurred on Thursday, November 5, 2020 at 15:00 UTC. Weekly media meetings are 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, @johnbillion, @sergeybiryukov, @desrosj, @hongnizzle

5.6 Remaining Tickets

#41648Alignment issue on media-new.php when browse uploader screen is active – Currently owned by @antpb. The ticketticket Created for both bug reports and feature development on the bug tracker. will be reviewed and committed by end of day November 6, 2020.

#22363Accents in attachment filenames should be sanitized@antpb will be reviewing ticket to confirm pending issues have been addressed before closing.

#51665wp_get_image_editor() ->save stopped creating the directory in 5.6-beta2-49360@mikeschroder has responded to ticket and there are still tasks to be completed.

#42663Imagick support for stream wrappersDev 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 pending for this ticket. Otherwise, if no notes are available, then the commit message describes the changes very well.

#51685: Media Element CSSCSS Cascading Style Sheets. Issue : Some layout display crop – Per @antpb, this ticket has recently moved to 5.6 as a fix to some UIUI User interface bits. Very recently refreshed. Will be completed by @antpb.

With these pending tickets addressed, the milestone will be cleared! Thank you everyone!

Props @antpb for proofreading and final review.

#core, #media, #summary

Dev Chat Summary: November 04 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, November 4, 2020, 05:00 UTC and Wednesday, November 4, 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/11/04/dev-chat-agenda-october-4th-november-2020/

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. 3 of 5.6 has been released!

WordPress 5.5.2 & 5.5.3 were also released. You can read up on the technical details in this post.

Highlighted Posts

Introducing auto-updates interface for Core major versions in WordPress 5.6

What’s next in Gutenberg? (November)

Updates from Component Maintainers/Focus Leads

General:
@sergeybiryukov reminded us that PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 release is scheduled for November 26. We have two weeks until November 17 (scheduled date for WordPress 5.6 RC1) to discover and fix any remaining issues. Please see the PHP 8 call for testing: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/. We need more testing on PHP 8, expanding test coverage, and creating tickets for any issues found.

Build/Test Tools:
@sergeybiryukov shared the following updates:

  • The test matrix on Travis was trimmed for older branches to remove the jobs that are no longer necessary. See #51705 for more details.
  • 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 test failures on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions were fixed, see #51670 for more details.

Open Floor

@ahmedchaion asked if there were any plans to have a New Contributor Meeting suited to APAC timezones. The group agreed that there’s:
1. No reason  we can’t have one if there are available contributors to run it
2. And that the regular APAC Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session fulfills that gap to some extent.
@thewebprincess asked if there were any core requirements for someone willing to run a new contributor meeting and if there was any documentation available. @sergeybiryukov followed up by stating there is no documentation currently available for this, but the following links might be helpful:

The group had a lively (and lengthy) discussion on the auto-updates UIUI User interface. The full transcript of the discussion can be viewed here.

@nalini highlighted the latest Month in WordPress post. And also shared the write-ups from the WordPress translation celebrations, adding that the Marketing and Polyglots teams are now working on questions and answers to encourage translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization., including about releases.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 11, 2020, 05:00 UTC and Wednesday, November 11, 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-2, #5-5-3, #5-6, #dev-chat, #summary

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

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, @mista-flo, @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 @mista-floand 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.. @mista-flo 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