Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No difference in behavior using different screen share protocols in shareAppContentToStage #2443

Open
markitosha opened this issue Aug 6, 2024 · 2 comments
Assignees
Labels
bug teams issue issue that has been reviewed and likely teams specific

Comments

@markitosha
Copy link

markitosha commented Aug 6, 2024

Hi Team,

I've been using the shareAppContentToStage method in the Microsoft Teams JavaScript client library and specified different sharing protocols in the shareControlOptions. However, I do not observe any difference in behavior when using these different protocols (e.g., ScreenShare vs Collaborative). From documentation, I would expect that ScreenShare protocol makes experience "read-only", without option to interact with the content on stage view, but I see no such thing.

Can you clarify what the expected differences should be when using different sharing protocols?

I'm using New Teams Client. @microsoft/teams-js library version: 2.24.0

Thank you!

@TrevorJoelHarris TrevorJoelHarris added the teams issue issue that has been reviewed and likely teams specific label Aug 6, 2024
@Nivedipa-MSFT
Copy link

Nivedipa-MSFT commented Aug 7, 2024

@markitosha - Thanks for reporting your issue. We will check and update you soon.

@Nivedipa-MSFT Nivedipa-MSFT self-assigned this Aug 12, 2024
@Nivedipa-MSFT
Copy link

Nivedipa-MSFT commented Aug 14, 2024

@markitosha - We are able to repro your issue. We have raised a bug for the same. We will let you know once we get any updates on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug teams issue issue that has been reviewed and likely teams specific
Projects
None yet
Development

No branches or pull requests

3 participants