As a user,
When I press the tab key,
I want menu items to highlight sequentially,
So that I can access them without using a mouse.

Suppose x-menu uses a core-menu but always shows the selected item at the top of the list:

<polymer-element name="x-menu" noscript>
  <template>
    <core-menu>
      <content select="core-item.core-selected"></content>
      <content select="core-item"></content>
    </core-menu>
  </template>
</polymer-element>

<x-menu>
  <core-item>Item 1</core-item>
  <core-item>Item 2</core-item>
  <core-item>Item 3</core-item>
  <core-item>Item 4</core-item>
</x-menu>

Click the third item (Item 3), so core-selector.selected is "2". Then click the third item again (Item 2). The selected item does not change; Item 3 is still ".core-selected". The "selected" attribute is set to 2 so it isn't considered a changed property.

Currently, there is no way prevent the submenu collapsing. It would be nice if all submenus could all be opened at the same time.

When loading a page with submenus from a cleared cache, the submenus don't open. Reloading the page appears to fix this. This shows up both in the core-menu demo and in the main docs menu on the side (the submenus, such as "Your first Polymer app" don't open).

https://www.polymer-project.org/components/core-menu/demo.html
https://www.polymer-project.org/docs/start/getting-the-code.html

See Polymer/old-docs-site#763 for more details.

1. Use appropriate aria roles for elements, e.g. role="menu" and role="menuitem". Elements currently use confusing roles like "img" or are missing roles.
2. Use meaningful aria labels, e.g. "arrow-drop-down" is too generic.
3. Use aria-activedescendant property for the actively selected menu item.

When you nested ` in IE9, it has various failure modes. Here's a barebones example of nested submenus (it's in branch "nested-submenus" if you check it out).

In that example, if you open up submenu 1, then 1A, only the first item from 1A shows up (it has three children, all <core-item>s).

If you open up 1, then 1B, none of the children show up (there should be three <core-item>s).

I can put the example up on a server if checking it out is a pain.

I've got a core-menu nested in paper-action-dialog > div > paper-dropdown-menu > paper-dropdown that I'm using to filter results from Firebase. Is there a way to keep it from updating the selected attribute until after the paper-action-dialog's affirmative button is tapped/clicked?

i can reproduce it in firefox 34 and 35beta (using clean profile).
for example on this page: https://www.polymer-project.org/components/core-elements/demo.html
or https://www.polymer-project.org/components/core-menu/demo.html

nothing happens when clicking on item, no any exceptions in console

in chrome it works as expected

UPD: also tested on firefox ESR 31 and the same behavior.
paper-tabs have almost the same behavior -- animation plays on click, but nothing more happens (and no any exceptions too)

UPD2: firefox nightly 37 -- the same behavior

UPD3: it don't reproduces in 0.4.2, problem started to reproduce only on 0.5.0 and the later versions.
i found only two commits between 0.4.2 and 0.5.0 (one of them to demofiles) and other is to deps:
5fdc874 . so that seems to be a problem in core-selector which came there from core-selection and which came there from polymer itself

I started trying to answer this SO thread when I realized that it does seem quite tricky to style the core-item's inside of a submenu such that they work the same in Chrome and Firefox.
http://stackoverflow.com/questions/25734090/polymer-core-submenu-styling-in-firefox

Is there a way to create a disabled menu item?
That is shown but not selectable ?

I'm using a core-menu with a few core-submenu all containing paper-items.
What I want to do is to add a to make is unselectable but still show in the menu and then CSS it to be greyed out.

I've been trying to use core-menu/core-submenu as a tree, and there are many problems. Before I start an elaborate writeup, I'd like an see to know

• Is using core-menu as a tree part of intended functionality or not?
• If not, are you planning on core-tree?

My suggestion is to add a tree property to core menu, and make it work. Tree is visually identical, only behavior differs.

Today this error started up. no changes from code that worked yesterday. Menu won't expanded to the sub items. pulled fresh copy of 'polymerchromeapp' (https://github.com/robdodson/polymerchromeapp.git) and same error appears here as well.

I have a menu with submenu and those submenus have nested submenus and when the item in the nested submenus are clicked the core-select event is triggered with the submenu no longer being selected. This only happens when "multi" is set to true

<core-menu multi="true">
   <core-submenu icon="check-box-outline-blank" label="Submenu 1">
      <core-item icon="check-box-outline-blank" label="Item 1"> </core-item>
      <core-item icon="check-box-outline-blank" label="Item 2"> </core-item>
      <core-submenu icon="check-box-outline-blank" label="Sub-Sub-Menu 1">
          <core-item icon="check-box-outline-blank" label="Item 1"> </core-item>
          <core-item icon="check-box-outline-blank" label="Item 2"> </core-item>
     </core-submenu>
   </core-submenu>
   <core-submenu icon="check-box-outline-blank" label="Submenu 2">
      <core-item icon="check-box-outline-blank" label="Item 1"> </core-item>
     <core-item icon="check-box-outline-blank" label="Item 2"> </core-item>
   </core-submenu>
</core-menu>

With core-item you can set class="font-scalable" which will make all measurements in "em"s, which allows for resizing menu items (and their padding), but it isn't possible to to set this attribute on <core-submenu> and propagate it through to its implicit <core-item>.