Kat

Thanks so much for submitting this proposal! I'm going to make some edits, including differentiating between what I think are true Expander scenarios and what are more like Flyout/MenuFlyout uses.

I've updated this proposal to include more details on the scope, a proposed API, and the following open question. - Do we need to support ExpandDirection in a v1 Expander?...

> It does seem like a basic function of the control @mdtauk do you see ExpandDirection other than downward being a common app scenario? The examples of Expander behaviors that...

> Yes, we need expand direction. There are many cases for using it and it would be an unnecessary breaking change to the control template after a v1 release to...

> Chat apps which load new list content from the bottom up being one of them maybe. @mdtauk I don't fully understand what you mean with this chat apps example...

@robloo > Another example I've used in the past are secondary, editable properties that should usually be hidden. These are shown at the bottom of an editor only when clicking...

> In the screenshots above, windows security has an expander for the antivirus section as well as the left navigation menu. This shows a very realistic use of the expander...

> 1: The screenshot above with the quick actions menu. Pretty sure that expands up. @JustABearOz thanks so much for bringing up these examples! For 1: I think this is...

@robloo Thank you for being honest with me! I understand that app developers should be able to determine what fits their use-case best, and that app compatibility is important. I'm...

Taking this proposal over from @kikisaints , thank you to everyone for your comments so far! I've updated the proposal, including the mock-up that @mdtauk shared. I'd particularly appreciate your...