Open klonos opened 8 years ago
Going to help with this, starting with responsive menu out of the box.
Keep in mind void menu exists in contrib On May 19, 2016 4:02 PM, "wesruv" notifications@github.com wrote:
Going to help with this, starting with responsive menu out of the box.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/backdrop/backdrop-issues/issues/1839#issuecomment-220446132
@wesruv :+1: ...let me know when you have a sandbox or private repo branch you want testing and feedback for.
@biolithic thanx, I wasn't aware of void_menu. Sounds like its features could/should be merged in special_menu_items:
Based off of the work done in special_menu_items and menu_firstchild
...I'm particularly interested in this:
...The benefit to using this module over special_menu_items for this is that your menus will not require any additional styling to account for the added span tags used by special_menu_items,...
So the issue here IIUC is that special_menu_items adds span tags that make it harder for the menu items provided by it to work out of the box with themes.
...and will be W3C valid because every anchor must have an href attribute.
This statement is not true : https://w3c.github.io/html/links.html#links-created-by-a-and-area-elements
NOTE The
href
attribute on<a>
and<area>
elements is not required; when those elements do not havehref
attributes they do not create hyperlinks.
I've just used Void Menu module for projects, that's all.
On Thu, May 19, 2016 at 6:34 PM, Gregory Netsas notifications@github.com wrote:
@wesruv https://github.com/wesruv 👍 ...let me know when you have a sandbox or private repo branch you want testing and feedback for.
@biolithic https://github.com/biolithic thanx, I wasn't aware of void_menu. Sounds like its features could/should be merged in special_menu_items:
Based off of the work done in special_menu_items and menu_firstchild
...I'm particularly interested in this:
...The benefit to using this module over special_menu_items for this is that your menus will not require any additional styling to account for the added span tags used by special_menu_items,...
So the issue here IIUC is that special_menu_items adds span tags that make it harder for the menu items provided by it to work out of the box with themes.
...and will be W3C valid because every anchor must have an href attribute.
This statement is not true : https://w3c.github.io/html/links.html#links-created-by-a-and-area-elements
NOTE The href attribute on and elements is not required; when those elements do not have href attributes they do not create hyperlinks.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/backdrop/backdrop-issues/issues/1839#issuecomment-220477343
Forgot to tick the "drop-down menus out of the box" task of the list 😉
This is a list of UX issues that are related to menus. Implementing these features will make us stand out when compared to Drupal and aim to cause the same awe and respect as layouts.
<nolink>
and<separator>
menu items).Not killer-features but resolving annoyances compared to the respective Drupal UX:
Not killer-features per se, but for "marketing purposes":
Feel free to add more issues with menu-related feature requests.