Gavin Barron

Closing this as the Teams MSAL2 Provider is deprecated

Closing this as it was resolved in #1784

Is this still an issue with the changes that were released in v3.0?

This is also impacting customers using Microsoft Graph Toolkit. We have a report from a customer on our repo that we have verified and tested as only being an issue...

I'll disagree that this is an a11y concern but wholeheartedly agree that extending this custom element to expose a validty state seems like a great idea.

I've done a little digging. We can tap into the native form validation by using a form associated control https://web.dev/articles/more-capable-form-controls https://css-tricks.com/creating-custom-form-controls-with-elementinternals/ The biggest drawback I've found thus far is that...

@sebastienlevert can we have a spec around what validation elements we're going to support on the people picker? Should we enable a range for multi selection? Are there other validation...

> My first comment would be to support it the same way the Fluent UI WC TextField works... https://fluent-components.azurewebsites.net/?path=/docs/components-text-field--text-field > > Should we be the one to handle all those...

This needs a redesign of the component to include visual labels for the form inputs

At present the best we can do is ensure that the display name is set correctly on the messages like this:  This is because, as @plasne noted...