Dev Chat Summary: February 8th (4.7.3 week 2)

This post summarizes the dev chat meeting from February 8th (agenda, Slack archive).

4.7.3 Schedule

• Still no release date scheduled for 4.7.3, but we began to assess tickets this week and will continue next week
• Goal is to finish scrubbing tickets in the milestone and plan for release timing
• 4.7.3 milestone Bug Scrub planned for February 13, 2017 at 10:00 CST in #core
  • Focus on tickets with no owner set to see if any can be picked up and worked towards a commit this month
  • Please attend the scrub if you have tickets you’d like to discuss

Customizer team update

• 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. team appreciates any help by looking at tickets and pitching in where you can
• Going through the customize component ticketticket Created for both bug reports and feature development on the bug tracker. backlog, identifying quick wins to add to the next release and then larger issues to tackle for the next major
• #21666 (Customizer reset/undo/revert) and #38707 (Customizer: Additional CSSCSS Cascading Style Sheets. highlight, revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., selection, per-page, pop-out) have initial designs and could use prototype and/or development help

Editor team update

• The Editor team will post a Make/Design update soon that features a couple of mockups showing 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. level and inline level controls as well as showing off one or more prototypes in various states of functionality.
• They’re working to get mockups and prototypes in a place where people can contribute to them, so keep an eye out for their post and please consider contributing and/or giving feedback.

REST API team update

• @rmccue is working on using the 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. to improve the editing experience relating to bulk actions in list views
• With limited team bandwidth, we’re evaluating existing usages of adminadmin (and super admin)-ajax to prioritize places where the API can be implemented to reduce inconsistency
• During 4.7 Quick Draft stalled out due to questions about content filtering that are happening on the admin-ajax path, and has resurfaced #21170 (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/. actions and filters) and #20491 (Introduce some JavaScript 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. functions)
• @kadamwhite is triaging open API bugs weekly, with a focus on normalizing inconsistencies
• #38323 (Reconsider $object_subtype handling in register_meta()) is priority from an API design standpoint, because the current behavior completely precludes using register_meta to model your data
• @jnylen0 has been tracking the multi-site API discussions, and there’s a post from that group up on the make/core blog
• Our biggest barrier is bandwidth; @rmccue & @kadamwhite are working on 1-2 priorities in their respective areas, but there’s a lot of docs and testing work, as well as POC for future endpoint types (like @westonruter is doing w/ Widgets) that could happen in parallel if there are interested parties
• Widgets (and therefore Sidebars, later) endpoints are priorities for @westonruter given the Customizer focus
• Menus endpoints are the other that comes up in conversation the most
• Once we have the first WP-Admin usage in place, we’ll be looking for more contributors to help spearhead more admin-ajax replacement; that’s higher-priority than new endpoints from a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. standpoint, in our opinion
• The REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. group meets on Mondays at 21:00 UTC in #core-restapi, we hope to see you there!

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Ticket(s)

• @pressupinc advocating for a fix for #34225 (Display correct dimensions for image sizes in media modal)
  • Seems to be caused by #35390 (image_constrain_size_for_editor() should not affect images generated on the front end when `large` size is used)
  • General issue is image sizes not displaying as they should in the Media modal
  • Reported #38906 (wp_get_attachment_image_src() sometimes gives incorrect width and height values)
  • Will check with Media team in #core-media

#4-7-3, #core, #dev-chat, #summary