Dev Chat Summary, June 10

Agenda, Slack log.

Menu Customizer Status Update (#)
@westonruter
The a11y review did not unveil any blockers, although it wasn’t done on the feature branch the team is currently working on. Introduction of a blocker there was deemed unlikely however. A new plugin version can’t be released since it’s now dependent on some core patches being applied.

For the rest of the requirements: The biggest blockers are almost complete, Customizer setting re-architecture and sub-menu drag & drop. The settings re-architecture has been integrated into JS for the nav menu items, allowing nav menus to be edited, added, removed all with 100% previewability and not making any changes to the DB. Once Save & Publish is done, any newly created nav menu items get inserted at that time. Same goes for nav menu deletion. The submenu drag & drop has been merged into the same branch and it is all working together now.

The biggest outstanding pieces are:

  • adding back the ability to add/remove entire menus
  • updating keyboard-accessible reordering to work with new menu settings
  • more unit testing for PHP, and write tests for JS

Estimated time of completion is June 11, which leaves 5 – 6 days to merge.

Admin UI (#)
@helen
Even more prep work has gone into list tables, now working on the responsive part on #32395. They have gotten some feedback so far, would love more even on the rough cuts. Helen will be at wordcamp philly’s contributor day this weekend, looking to knock through a bunch of the low hanging fruit on the screen sweep spreadsheet, and find takers for some make-flow tickets (#29906 in particular). She has some catch up to do with other contributors on visual regression testing and media-new, which will happen at tomorrow’s meeting.

Network Admin UI (#)
@jeremyfelt

Objectives from last week:

  • #32434 is in. Jeremy is still poking at #22383 and #32503 with a target of this evening.
  • They had no additional iterations on WP_Network and WP_Network_Query, but @jjj is working on having something this week.
  • Did not yet generate discussion around HTTPS. Moving this objective along to this week.
  • They made quite a bit of progress with flows. @kraft added Nexus and @earnjam has iPad screencaptures he will be publishing shortly. Their next push is to start creating tickets. Jeremy wrote a post to try and drum up support – https://make.wordpress.org/core/2015/06/05/help-test-and-capture-the-network-admin-ui/ – and they had a handful of people hop in. Pretty optimistic that they’ll start making progress here, especially with a couple contributor days this weekend.

Objectives for this week:

  • New tickets to address found issues in flow. These issues logged in the screen sweep spreadsheet.
  • Iterations on WP_Site and WP_Network. Discussion around iterations.
  • #22383 and #32503 committed.
  • Write post, generate discussion around HTTPS in multisite.

Better Passwords (#)
@markjaquith
Mark turned the plugin into a patch for the new UI. After a cleanup, that can land, and we can iterate a bit, as well as tackle the new user password flow, which is different. The expiration of reset links (#32429) needs testing (human and unit), before that lands. And the “notify users of password and email changes” patch (#32430) needs a review on the hooks in it. I’m not sure we’re passing the right things along. Like, email instead of the whole user array.

Favicons (Site Icon) (#)
@johnbillion
There’s been a status update on make/core. It’s looking like #29211 would be a better approach to a reusable control with image cropping functionality. So John is wondering whether we should aim for 29211 for 4.3 and site icon for 4.4. On the topic of using the Customizer or not: much of the image cropping control for the header image is also used on the old header image screen (it’s mostly media library and ajax functionality), so it’s not necessarily tied to being a customizer control.
Let’s meet today June 11 2015, 20:00 UTC to discuss what a good approach could look like.

Next chat will be on June 17 2015, 20:00 UTC

#4-3, #meeting