[wp-trac] [WordPress Trac] #23595: Nav Menus Testing
WordPress Trac
noreply at wordpress.org
Sat Feb 23 18:50:27 UTC 2013
#23595: Nav Menus Testing
-------------------------------------+------------------------------
Reporter: bobbravo2 | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Menus | Version: trunk
Severity: normal | Resolution:
Keywords: needs-testing 3.6-menus |
-------------------------------------+------------------------------
Comment (by DrewAPicture):
Replying to [ticket:23595 bobbravo2]:
> IE7 Shows some CSS bugs: http://cl.ly/image/142s2y2Y452w Functionally
speaking, IE7 works.[[BR]] If we need to support IE7, let me know and I'll
take a stab at the browser quirks.
The rule of thumb with IE7, is
[https://irclogs.wordpress.org/chanlog.php?channel=wordpress-
dev&day=2013-02-20&sort=asc#m559725 "not horribly broken"].
> One UX note is that the checkbox[[BR]]
[[Image(http://f.cl.ly/items/3K373n2t0P2k3p2h1b3d/Screen%20Shot%202013-02-23%20at%2010.03.13%20AM.png)]]
[[BR]]
> feels unnecessary if `(menus == 1 && theme_locations == 1`)
>
> '''The UX seems broken when I "Create Menu" on my fresh new !WordPress
site, and then go to the homepage and see the fallback pages menu.''' The
1 menu should automatically be used, and the checkboxes only shown when
`$menus > 1`.
I disagree with hiding the locations at all, especially since we don't
have the dedicated locations meta box anymore. Users need to be able to
un-assign the one menu from the one location.
> I tried applying the 23119.31.refresh.patch patch as well, but there
were some missing files, let me know which one you'd like more testing on,
or if I should just test trunk.
All accepted changes were committed from #23119 so we're testing on trunk.
See also: #23449, #23450
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23595#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list