search

FSWebDevBook / speedscore-dev

This the author's sandbox repo for the SpeedScore personal speedgolf app developed in the book.
0 stars 0 forks source link

Should the menu implement an application menu pattern? #4

Open anevins12 opened 3 years ago

anevins12 commented 3 years ago

Should the main menu implement the application menu design pattern?

The main menu still navigates to other parts of the website/ app, it is still a navigation menu. How I understand the application menu pattern is that this is used when the majorty of actions are button-like and performn things like turning settings on and off. Example of an application menu: https://www.w3.org/WAI/tutorials/menus/application-menus-code/ b6473812-5a83-4e81-ad00-45357175098e

chundhau commented 3 years ago

@anevins12 Thanks for the tip! I believe that I am implementing the application menu pattern already. I am using role=menu for the top-level <ul> and role=menu for the subsidiary <li> elements. The only question that I have is how to deal with the "Menu Title" element -- the user's picture and name. Presently, it is an <li> element but it does NOT have role=menuitem. I am thinking that the User's picture and name could eventually be used to access the user's profile settings. However, that may not be standard. A better approach may be to include a "Profile" or "Profile Settings" menu item.

What would you suggest here?

anevins12 commented 3 years ago

After looking over your reply and my original comment, I think you're right here to use the implementation you have and there's nothing to do.