5/15/2023 0 Comments Tiny screen marker tool![]() deciding whether to include "local tasks" such as add/edit/view, as Admin Menu does). Evaluation on "how deep is deep" in terms of the menu (e.g.Likely numerous spin-off issues, based on how users react to the toolbar when interacting with it on a daily basis, possibly including: Dependency: #1815602: Introduce a polyfill for matchMedia.Caching strategy for performance: #1814932: Caching strategy for D8 toolbar.Accessibility review to ensure there are no critical regressions.An in-depth code review of said patch, including for JS/CSS standards, documentation standards, customizability, etc. ![]() Get a "needs review" patch up once the spec is locked down (all patches to-date have been "needs work" as they were merely prototyping the design for feedback).At the moment, the biggest blocker to achieving this seems to be getting the horizontal navigation to show the top-level navigation only, without sub-navigation, which would allow us to save discussion on how this should be done for a follow-up. Get to "I can live with this" on the design ( not perfection) so we can freeze the spec. ![]() There remains disagreement on what "critical design blockers" are, however.Īt the moment, here is my (webchick)'s best read of the situation, and is NOT guaranteed to be correct, but here it is: Therefore, the recommendation from the folks working on this is to eliminate any critical design blockers ASAP, so that it can be iterated on based on feedback from more than the handful of people active in this issue. Every moment that we spend arguing in this issue trying to achieve design perfection is a moment we are not spending getting "real world" user experience that could help inform further design changes on the basis of data, rather than opinions. Community consensus is not yet achieved, and it is quite clear that it cannot be achieved in time for feature freeze, allowing time for a workable patch that passes code review by then. The issue has yet to even receive a single "needs review" patch because of this constantly changing spec, despite having been worked on and iterated on for over 2 months. Remaining tasksīy far, the biggest thing that puts this issue in peril of being solved before feature freeze is continued disagreement over the spec and design. In mobile view these will collapse down to just an icon. The desktop orientation also better exposes the idea of the "action zone" of the toolbar (the black part) where modules such as Shortcut, Menu, User, and Search (shown) can expose their own things to add to the toolbar. vertical orientation manually, if one so chooses). When the width of the viewport exceeds a given size, the orientation flips to horizontal instead (although there are icons on the far right that can be used to toggle horizontal vs. The orientation switching implementation hooks off a configurable breakpoint from the Breakpoint module that was added to Drupal 8 recently. leave as-is, or do what Admin Menu does, or.) In horizontal / desktop mode, only the top-level navigation items are shown (parity with current D7 & D8 toolbar), rather than the sub-navigation, in order to defer discussion about what to do about drill-down on desktop to a follow-up issue (e.g. Similarly, the icons are an important facet of the design they are used to communicate key items in the top-level bar where there is not enough space to put textual descriptions of everything. or more levels deep in order to get from where you are now to one level above. Support of "drill-down" is an important facet of the mobile design it's incredibly annoying on a mobile device to have to click 1, 2, 3, 4. When drilling down, the navigation looks like this:ĩ levels of navigation are supported, which is the maximum that the menu system supports. On a mobile device, the toolbar extends vertically down the page, showing the top-level navigation by default (Content, Structure, and so on) along with icons (implemented by scalable SVG vector images that both a) scale to any screen dimensions, and b) are simply a CSS override away from customization) and arrow symbols that allow people to drill down further into the navigation. Proposed resolutionĪfter numerous rounds of prototyping and more prototyping and revision after revision after revision of the design based on community feedback and usability testing, the current design (as of ) looks like this: It's not acceptable to ship Drupal 8 like this. The mobile initiative is one of the strategic initiatives for Drupal 8. You can find many different depictions of the general rise of mobile that's exploding all over the world. In Drupal 8, navigating as an administrative user on a cell phone looks like this: This issue is too long to be loading frequently. Please follow post-commit follow up activity here: #1846970: Responsive Toolbar follow-ups
0 Comments
Leave a Reply. |