Core Dev chat notes for Feb 17


Schedule Notes, Status Updates, Open Floor

Schedule Notes

  • Today is the feature plugin merge deadline!
  • Customizer Responsive Preview was merged. Thanks to everyone who helped out there!
  • The first beta is scheduled for release next week! This means that any remaining features/enhancements need to land before then.
  • @chriscct7 has been leading daily scrubs of these tickets; ticket owners should post an updates on the ticket status.

Status Updates

  • Image Improvements: @joemcgill
    • Improving the performance of wp_uploads_dir() (#34359). @azaozz committed this and left the ticket open for possible function name changes or additional tests.
    • PDF Thumbnails (#31050) are close. Creates a thumbnail version of uploaded PDFs. Feedback would be welcome, particularly from UI focused folks and around how the PDF thumbs’ meta is stored. This needs careful consideration as it would be a model for any other thumbnails for non-image types. The intent for this release is to improve the editor experience a bit, which the thumbnails would achieve.
    • Improving default image compression (#33642): Looks like we should be able to reduce the default compression quality and see big improvements in file sizes without a perceptible loss in image quality. Look for a blog post requesting feedback later this week to make sure core is ok with changing the default quality for intermediate sizes.
  • Customizer: @westonruter, @celloexpressions
    • Published a post on Make Core that detailed Selective Refresh in the Customizer. Hoping to get feedback on the implementation for nav menus and widget, on the framework for theme/plugin authors to register their own partials for selective refresh, and also for a general code audit for security and docs. In the process right now of creating that core patch and will attach to the ticket #27355. I’m also in the middle of writing unit tests, but help there would be appreciated.
  • Multisite/WP_Site: @jeremyfelt
    • No big updates. Started making progress on a few tickets today. Nothing negative or breaking with the new `WP_Site`, though we’ll continue to keep testing and looking for ways to improve. @spacedmonkey has also submitted a ticket for `WP_Site_Query` which will be fun.
  • Editor: @azaozz, @iseulde
    • Thinking and testing if the inline link dialog should have two fields, URL and link text, like the modal. Seems the more streamlined version with just the URL is better.
    • Another change that’s coming is to add autocomplete to the modal instead of the infinite scroll at the bottom. That gives plugins some more space to add additional “advanced” settings and simplifies it/makes it consistent with the inline dialog.

Open Floor

  • @mike Wanted to discuss Theme Logo Support (#33755).  @obenland was kind enough to do a port of the feature from Jetpack, and there’s been good conversation happening on the ticket. It needs testing. Can be tested with Twentysixteen and a patch and with any theme that supports Jetpack site logos. Needs work on this suggestion.
  • @ocean90 raised Unifying permission error messages (#34521). Right now we use a variety of  language for error messages and this ticket is about unifying and clarifying that language. @ocean90 asked for opinions about the best language to inform users they are not allowed to perform some action. Extensive discussion ensued and Sorry, you are not allowed to… seemed to be the top choice.

Full meeting log available in Slack.


#4-5, #dev-chat, #meeting-notes