Dev Chat Summary: October 26 (4.7 week 10)

This post summarizes the dev chat meeting from October 26th (Slack archive).

Reminders

• Schedule: Today is/tomorrow will be 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 day. This means: no more enhancements and feature requests open for 4.7 (this sometimes means things with initial commits become “tasks”), and then from here on out we only work on 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. It should be noted that bug fixes in this context are a little broader than what you’d call a bug fix in a bug tracker – it includes polish for new features. Typically that means UIUI User interface and UXUX User experience polish, but of course UX includes dev UX.
• Tickets: There are currently 83 tickets in the 4.7 milestone. This is 27 fewer than last week. 🎉However, in just 3 short weeks, this needs to be zero. For any tickets you’ve moved into the milestone, please make sure these are active tickets with some kind of activity in the last 7 days.
• Bug Scrubs: Several scrubs have been / are planned for this week. Scrubs remaining this week are planned for Thursday, October 27th 9:30am CDT for 2.5 hours and Friday, October 28th 9:30am CDT for 2.5 hours. If you have interest in helping run a scrub and ensure tickets land in 4.7, then please reach out to @jbpaul17 or @jorbin and we’ll find a time & scrub focus that works best for you.

Remaining Feature Requests and Enhancements

• #27159: Removing TinyMCE buttons to improve user experience
  • Closing this as fixed. Bugs can go in new tickets.
• #36211: TinyMCE: allow pasting in image captions
  • This is something that needs testing attention but doesn’t actually need to be open. Closing that too.
• #38488: Twenty Seventeen: Replace remaining Genericons with Font Awesome icons
• #38502: TwentySeventeen: unnecessary l10nL10n Localization, or the act of translating code into one's own language. Also see internationalization. Often written with an uppercase L so it is not confused with the capital letter i or the numeral 1. WordPress has a capable and dynamic group of polyglots who take WordPress to more than 70 different locales. variables
  • Both of these Twenty Seventeen are likely bugs, will re-classify them.
• #38490: Add settings to the /wp/v2/settings endpoint that are in the WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ api
  • @rachelbaker owns this one for commit.
• #38504: Term query endpoints should use WP_Term_Query
  • @joehoyle will merge this one today.
• #38342: Quick Draft: Leverage 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/. endpoints
  • Another lingering thing around beta 1 is the request that something in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. leverage the REST API – there’s some discussion around this going on in #core-restapi.
  • REST API team will put feedback on the Quick Draft ticketticket Created for both bug reports and feature development on the bug tracker. with our thoughts on these questions.

Defects and Tasks

• #26601: Inappropriate content in headings on adminadmin (and super admin) screens
  • The main H1 headings in the admin screens contain stuff that shouldn’t be there (“Add New” button, search string text, in some cases even the search input field). Headings should be just headings and all that stuff should be moved out from them.
  • The latest 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. a proof of concept on just 2 screens, trying to find a way to proceed step by step and (hopefully) avoid any breakage.
  • “Being able to do it one instance at a time will make it much more manageable, so that we could hopefully get it started in 4.7 and completed in 4.8.” — @joedolson
  • We need some eyes on the patch, to see if the new approach is good enough and check for any potential layout breakage.
  • We’d like to hear if there’s consensus to merge it in core now, thinking that beta is maybe the best way to test it (it can be reverted at any time). If/when merged, some testing and comments on the ticket would be very appreciated too.
• #38378: Remove the `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.` parameter in the Post Controller
  • Exposing filter as a shim for WP_Query provided useful functionality that’s still unsupported by the “first-party” 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. query parameters (complex date queries for example), at the expense of a very broad back-compat surface we then need to maintain.
  • We long ago decided not to extend filter-like shims on other endpoints; for consistency we had proposed removing it everywhere. But it’s been around since < v1, and removing it will be a more breaking change for integrating developers than anything else in the 4.7 REST API.
  • So the question is: remove, or keep in and live with it?
  • This is really about supporting people who have built stuff on v2. If people were not already using it, we’d remove it and just recommend the use of the top level args like `?per_page=x`, so for me, it’s a question of supporting those existing users.
  • Agreed approach will be 1: remove filter from core; 2: make sure it’s in the 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, and make sure the versions play well together; and 3: throw doing_it_wrong.
• #38494: WP REST API: Stale Post Status on DELETE of Post
  • What happens when you DELETE something is pretty inconsistent. When you delete a revision, you just get true. When you delete a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. or 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.), you have to specify force=true or you get an error.
  • Agreement: this something we’re comfortable discussing & addressing later.
• #38114: Make it easier to visualize where to put your content in a given theme (aka “dummy content”)
  • This is marked as a task, but really needs a first commit before beta 1.
  • No existing code yet and getting a commit before beta 1 seems like a stretch.
• #38172: Enable Video Headers in Custom Headers
  • This is marked as a task, but really needs a first commit before beta 1.
  • Video headers is close to being ready for an initial commit, with adjustments to come in beta.
  • There are a couple of quick tweaks we can make like making them only show on the front page in the core output functions, for example.
  • The late push on video headers has been fantastic, but it needs more eyes and testing.
  • The biggest concern is file size, and increasing page file size for a large amount of users.
  • Not loading video on screens narrower than X, only showing video on the frontpage, adding classes to the output markup for themes would be quick fixes we can make right away.
  • By having it in Core, it encourages themes to do it in a preferred way. And more importantly, provides consistent UX in the 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. for users from theme to theme.
  • @celloexpressions to work on revised patch, @joemcgill to review for commit
• #38387: Twenty Seventeen: Keyboard navigation on Safari 10
  • We would appreciate some other testing this patch; its been tested, but could use some more eyes on it.

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