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

During screen share, mouse pointer is included in video stream even when another window overlays the shared window #32764

Open
6 tasks
ConwayLS opened this issue Jan 28, 2025 · 0 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Calling Server customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@ConwayLS
Copy link

  • @azure/communication-calling:
  • 1.32.1:
  • Windows:
  • nodejs
    • version:
  • browser
    • name/version:
  • typescript
    • version:
  • Is the bug related to documentation in

Describe the bug
When sharing a window, the mouse pointer is included in the shared screen video stream, even if another window is on top of the shared window in the Z order. It seems that the system should realize that the mouse is no longer active in the shared window and then not include it in the shared screen video stream.

To Reproduce
Steps to reproduce the behavior:

  1. Get into a call with user A and B.
  2. User A shares a window
  3. User A overlaps the shared window with a second window
  4. User A moves the mouse in the second window, within the area that is overlapping the shared window
  5. Notice on User B's side that the shared screen video stream is still showing the mouse pointer.

Expected behavior
It is expected that when the mouse is within the second (overlapping) window, it would not be included in the shared screen video stream. It is misleading.

Screenshots
None

Additional context
None

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 28, 2025
@jeremymeng jeremymeng added Client This issue points to a problem in the data-plane of the library. Communication - Calling Server labels Jan 28, 2025
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Calling Server customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants