I am looking to create a menu bar with a specic type of "action"
Similar to the bar on this website
BBC Sport
Its totally static and has no dynamic or "pop out" sections. When the top menu is clicked the page will re-load and display the lower level in a diffrent colour.
Can this be achived with the Standard ASP:Menu control?
I am not a big fan of the pop out feature however I do not want all my options to be visible to my users at root
Hope that makes sense
Check out this basic ASP.Net Menu control page. You can click on the "Run" buttons to see very basic versions of the menus.
The advantage of using this particular approach is that you can tie it to a sitemap, so you don't have to keep updating the menu code. You just add the page(s) to the sitemap, and the menu picks it up.
You can also dynamically link the menu to different sitemaps, such as one for the admin menu and another for regular users' menu.
The Menu control is in the navigation section of the toolbox.
To experiment with the built-in functionality (before writing your own code to do what it will do for you), just drag and drop a menu control onto your form. Then, use the common tasks menu to:
autoformat -- good for quick & dirty because it sets hoverstyle too
set the data source
set the view type (static or dynamic)
define menu items with an editor
work with templates to set appearance
You have to go to properties to set menu appearance.
Related
I have a design that displays a list of content that you can filter by different categories. Each filter is displayed in a dropdown menu that lets you choose one or more options, which when activated (either through click or keyboard), will update the results on the page. The page url does not change in response to the filter and there is no "submit" button to apply the filter.
I'm confused which ARIA pattern to use: Menu (with menu/menuitem roles) or Combobox (with listbox/option roles).
In my opinion you should go with a combobox.
Otherwise, it should be a menubar rather than menu:
A menu that is visually persistent is a menubar.
Managing focus
Aside from the question which role to use, you need to decide whether to manage focus or not. It is recommended (should) for menu and menubar, which would mean that the whole bar only has one tab stop, and navigation between the single dropdowns is done via arrow keys.
Website or application?
This depends on how much your site feels like an application overall. If it’s more of a website, keyboard users in general are more accustomed to tabbing than to managed focus. For users it is sometimes a surprise that you need to navigate within components by means of arrow keys.
If there are other composite widgets as well that manage focus, you absolutely could do so for this part as well.
Responsive Design
A menubar should allow left and right arrow keys to navigate the filters, and up and down to focus the options. Managing focus would get complicated with Responsive Design: Once items wrap, it becomes less obvious how to navigate to them.
Actions vs Selections
A menu is usually used for actions. To quote some references (emphasis mine):
A menu is a widget that offers a list of choices to the user, such as a set of actions or functions.
– Menu or Menu bar pattern
The WAI ARIA standard defines an actual `nole="menu"' widget, but this is specific to application-like menus which trigger actions or functions.
– Bootstrap
Since the filters only allow choosing options, and not executing commands or functions, I would rather go with combobox.
Searchability
Combobox also implies that it’s a flat list of options, maybe grouped. This is immediately known. A menu can potentially have sub menus, so it’s less clear what to expect when opening a filter list.
Since combobox is a flat list, users can type Printable characters to directly jump to a list item. This is not the expectation for menus.
Show the user’s selection
Since the filters close once a selection is made, it is best practice to display the chosen value or values in the closed item. Also known as the Visibility of System Status.
A combobox will do so, and screen readers would even announce the current choice without opening the list. A menu does not have that behaviour.
I new to Blackberry and qt. I want to make a drop down menu like android drop down menu. I had search and found nothing. I only found about drop down list not drop down menu. Please help me.
The menu choices for a Cascades application:
Action menu (shown on the bottom action bar if you app has one configured as well has swiping from the right)
Context menu (press and hold an item to display a partial view, hold/drag out to reveal complete menu)
Application menu (up to five menu items at the top of your app)
Custom menu (whatever you can think up by accessing the bb::system::MenuManager)
You can read more about all the menus HERE
If you want something that is specifically like android's drop down menu you can always explore option #4 and make a custom one.
I have a responsive layout where the desktop view shows search, logo, login. In the xs/mobile view I would like the search and login to collapse into buttons. I can get this layout working just fine. The issue is that in the desktop view, I have a Search Options link that opens a popover with tabbed search forms. I'd like to still have that once you click the collapsed search button. My issue is that the popover is being created inside the tag instead of after it.
How can I set it up so that there is one div holding the search options that can be displayed from either the desktop view (search bar, Go button, search options link) as well as the mobile view (just a button with a search icon).
I am not tied to the popover- I just liked the look of it and I am not sure how to deal with the data-toggle as it currently is set to "collapse" and it seems I might need it to be able to also somehow be set to "dropdown."
Hopefully there is an easier/better way to do this!
i am using menu controls on my master-page and have used sitemap data-source to populate it. It shows main node on menu. is there a way that it populates the menu with sub-nodes of my master node rather than using default "home" ie masternode as starting menu item.
when you create a site map, you always design your properties in a way that it suites your web needs, They will contain, your starting node, name display, view state and autopostback.
Check your sipemapdatasource properties and your will know how to do that
You just simply put the ShowStartingNode = False in the SiteMapDataSource properties.
IT was simpler than i thoght.
i have a image menu within my asp.net website. i want to include an easy solution for hoverover functionality. for example, menu item one would dispay 1.jpg on page load and hover1.jpg when a user hovers their mouse over the image. thanks for any support.
You can do this easily via javascript :
http://www.webdevelopersnotes.com/tutorials/javascript/javascript_image_change_functions.php3