All CLA requirements met.

Hey, thanks for the PR! I've added it to our project kanban even though it's still in draft - this is to keep it on our radar, not to pressure you on time. 🙂

Hi @corinagum,

I see that BotFramework-WebChat-CI-PR has failed below above, but when I try to click on details I get a 401 Unauthorized error.

Are you able to screenshot what the failure is please, or give me access or similar?

Note, I'm just waiting for a response to check my understanding ...;)

Many thanks,

Nick

@nfreear There was one failing test due to timeout as opposed to broken code. I've re-run the pipeline with the expectation that we'll get 100% pass. I'll check on it periodically and rerun if we get more timeouts.

Tests now passing

Thanks @corinagum !

@nfreear ping! How's it going? We'd definitely like to get your PR in when you're done with it!

I updated the PR as we commented in the original issue.

Instead of using styleOptions, we prefer role attribute, as commented in #3658.

useContainerRole is not needed because:

• Hooks are added only if it benefit developers when they are in composition mode
  • Composition mode = developer bring their own UI, but using Web Chat business logic layer and maybe part of UIs from Web Chat
• For this feature, it's very likely that the role prop is being used only once and reading/sharing the value is not a common scenario for composition mode

Hi @corinagum and @compulim,

Apologies I left this unfinished (caught up in other work I'm afraid :() ... And, thank you for modifying @compulim -- I can see how the modifications make sense!

Best wishes,

Nick

Totally understand about getting caught up! Similarly, we love community contributions but it's hard to fit it into our day-to-day schedule, haha. We'd love your participation in other changes if you ever have the time! Thanks again for your help.