Improving Mobile Flow in 4.2

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Over on make/flow, we’ve been flow testing coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., posting visual records, and opening tickets tagged make-flow. During 4.2, we’re going to highlight a couple of these flow tickets every week, with an emphasis on mobile. Here is a small selection of mobile make-flow tickets to consider for 4.2. From log in, to the toolbar and adminadmin (and super admin) menus, on to the editor media buttons, these tickets note some of the annoying little UXUX User experience issues that impede flow on phones. Fixing these would improve our mobile flows significantly.

The logo headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. on the log in screen is too large a tap target
https://core.trac.wordpress.org/ticket/31185

Submenus can’t be dismissed on mobile.
https://core.trac.wordpress.org/ticket/29906

Hide Media Buttons on small screens
https://core.trac.wordpress.org/ticket/29989

Prevent device keyboard from displaying after selecting an image in TinyMCE
https://core.trac.wordpress.org/ticket/31162

Allow swiping the admin menu open and closed on touch devices
https://core.trac.wordpress.org/ticket/31187

If you’re curious about Flow and Visual Records, check out the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. on make/flow, the Flow Glossary, and the #core-flow 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.

#4-2, #flow, #mobile

Nick Halsey 7:32 am on February 1, 2015

Just added a new 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. for improving 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. experience on mobile – #28784 – could use some help there to get that into 4.2 as well. If someone has time to record some Customizer flows on mobile that would be great.
- Ryan Boren 5:22 pm on February 2, 2015
  
  I’ll do some vizrecs with and without the 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..

Comments are closed.

Welcome!

Communication

Share this: