Open michael-hawker opened 4 years ago
FYI @skendrot, please add on anything here if I've missed anything from the previous discussion in the toolkit PR.
@adambarlow FYI
Thanks @michael-hawker. These are great additions to consider on the menubar. Let me circle around with folks and get back on potential timelines here.
@adambarlow you can see where I do this comparison investigation from my live stream highlight here. That can also help highlight more easily some of the oddities I encountered in the Gallery app.
@michael-hawker Looks good! I would say that being an ItemsControl isn't a requirement so long as it can bind items and children (hierarchical items).
Thanks @skendrot, yeah I used the words 'like a' to signify I don't have to see it actually inheriting from ItemsControl
(breaking change) as long as we can satisfy those same scenarios for data binding/templating.
Added another gap from #2740 identified about Click/Command for MenuBarItem.
@adambarlow any update on this?
Note: We are not migrating the Menu
control to the Windows Community Toolkit v8.0 release. Therefore, anyone migrating from our old control to the WinUI 2/3 versions may encounter these issues still. FYI @bpulliam @chigy.
Proposal: MenuBar improvements for parity with Windows Community Toolkit
Summary
A while back we deprecated the Menu control in the Windows Community Toolkit when MenuBar was added to WinUI. However, during our PR to remove the feature in our 6.0 release it was brought up that the MenuBar control doesn't have parity with the WinUI one, so we held off on removing it, see discussion in PR.
This proposal is about ensuring we can close the feature gap and remove the Menu control from the Toolkit hopefully later this summer?
Rationale
Scope
IsOpened
Property for Menu and Selected/Opened MenuItemsImportant Notes
Was noticing some odd behavior in the Gallery, maybe because the menu's aren't at the top-level navigation?
Open Questions