A few dropdown issues about terracotta HOT 3 CLOSED

1. Yes this has been a long issue. Not sure but the current workaround for this is. I'll probably do a research
2. Might have missed that, to fix.
3. I'm sure it should refocus on the last focused element (before opening).
4. I was sure it should close itself but probably there was some regression. I'll check it out again

from terracotta.

@Brendan-csel after re-evaluation here are some of my thoughts

Primarily, the dropdown-menu example is supposed to be just a Popover + Menu demo. The thing about this is that there's no predefined behavior for when these two are combined, and thus it is left to the user implementation to control the visual state of the dropdown.

1. I was thinking of the Listbox behavior mistakenly. This is the correct behavior due to how focus works with scrolling.
2. According to the WAI-ARIA definition of Menu:

Disabled menu items are focusable but cannot be activated.

So the current behavior is correct.

3. This might be fixable.

4. This is left for user to implement.

from terracotta.

Thanks @lxsmnsyc.

I'm trying out some other options but for the sake of completely documenting this, here is a stackblitz link

And a capture of me focusing the button, pressing down a few times (and not getting past the disabled item), then pressing escape.

from terracotta.