Gavin Barron

Thanks for your repro @araver I took a look and cut it back further and then worked out wht I think is going on for you. In React whenenver a...

Well that is an interesting change. One that _could_ be considered a breaking change as it will change the nature of the data returned for these queries. I'll admit a...

Apologies for the delay getting back to you here @HiltonGiesenow I've spent a little time to try and comprehend this issue a bit more, bear with me as a I...

Thanks for the additional context. I see the problem regarding the PersonCard now, and yes, we should try to address this friction point. Regarding the contact user type, it includes...

Almost. For user-type `any` there should be no need to expand the scope of the search as it uses the `findUsers` path already. Thanks @HiltonGiesenow

Hi @JeffKam-Stn I followed your reproduction steps and found that the team chat and calling links worked as expected:   I did run yarn and yarn build in the...

@JeffKam-Stn thank you for the reproduction. It appears that this is a Chrome specific issue as it's working as expected in Edge 104 but not in Chrome 104. Interestingly I...

Edit: I was mistaken, my tests were invalid as there were cached credentials triggering the logged in behavior. I cannot understand how the two cases behave so differently though.

Nice catch @musale Perhaps we should be looking at using padding-block or padding-inline for things like this to better support rtl writing direction?

This may be related to the behavior we saw during development of the new version of the Agenda component were FluentUI cards use a `contain: content` CSS rule. This was...