[wp-testers] WooNav Issues

[Andrew Nacin]

Much of the navigation is broken functionality and unpolished UI. It
just landed in trunk and we're getting the schema settled first.

You're welcome to comment on
http://core.trac.wordpress.org/ticket/11817 as you find things,
especially as it progresses. Thanks for the feedback.


On 2/21/10, John O'Nolan <john at onolan.org> wrote:
> Hi Guys,
> Some notes on the Woo Custom Nav that was implemented over the weekend:
>
> Grammatical Error
> When enabling, the status message says:
> "(site name)s Custom Menu has been updated!"
>
> This should say:
> "(site name)'s Custom Menu has been updated!"
> Where the added apostrophe is possessive.
>
> Confusing Element
> It is unclear that the user is expected to "add a menu" prior to
> creating menu items. This should either have a large call to action,
> or the other options should not be available until a menu has been
> created.
> When adding menu items without having first "created a menu", clicking
> on "save all changes" causes all the menu-items to be immediately
> deleted.
>
> Links Opening in a New Window
> When adding a custom url to the menu, the default functionality
> assigned to "open link in a new window" is "yes" - causing any site
> using this to immediately fail xhtml1.0 strict validation, as well as
> being of questionable usability value!
>
> Feature Request
> It would be incredibly helpful if the "edit menu item" options
> included a way of adding a custom class to the <li>
>
> John
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>