[wp-trac] [WordPress Trac] #32710: Customizer Menus: improve the "no results found" message

[WordPress Trac]

#32710: Customizer Menus: improve the "no results found" message
--------------------------+---------------------------
 Reporter:  designsimply  |       Owner:  designsimply
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  4.3
Component:  Customize     |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  ui
--------------------------+---------------------------

Comment (by celloexpressions):

 Please don't hide the other sections when search results are shown on a
 hunch. That would be hiding all of the UI that lets you get to other ways
 of adding items besides search, and it sounds like a visual UI issue
 that's influencing a massive UX change. Clearing the search field to get
 those sections back is not intuitive, and potentially not something users
 would do - if they don't see any UI but the search box and the no results
 message, they'll probably try a different search with similar terms,
 potentially never clearing it fully. Because the available menu items
 panel's state is generally persisted when it's closed and reopened, this
 could cause frustrated users to lose access to the navigation to menu item
 types until they close and reopen the Customizer.

 If such a change were to be made it would need extensive user testing and
 analysis before being made. It's probably way too late in this cycle to
 make this sort of a change, which could have major unexpected consequences
 based on how things have gone with this area so far in terms of UX. I'd
 strongly recommend sticking to the simpler approach of improved help text
 for 4.3, then we can re-evaluate, run further user tests, and continue
 iterating on the experience in the future when we have more time to make
 fully-considered and tested changes. Also note that this ticket has been
 focused on improving the no results found string from the beginning, and
 this issue seems out of that scope.

 I'm fine with `No results found.` and then whatever the agreed-upon
 expanded explanation paragraph is.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32710#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform