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

setContentProtection(true) does not work in the always-on-top mode #896

Closed
cgri1 opened this issue Aug 11, 2023 · 3 comments
Closed

setContentProtection(true) does not work in the always-on-top mode #896

cgri1 opened this issue Aug 11, 2023 · 3 comments
Labels
macOS Issues affecting macOS stale

Comments

@cgri1
Copy link

cgri1 commented Aug 11, 2023

setContentProtection(true) does not work in the always-on-top mode

Description


The moderator starts a meeting in a browser. The desktop client joins the meeting. The desktop client shares a screen. And then the client clicks outlier of the application. The always-on-top mode will be active. The moderator sees the block of always-on-top mode. Normally, the moderator must not see the block because of the function setContentProtection(true).

Current behavior


The moderator sees the block of always-on-top mode.

Expected Behavior


the moderator must not see the block because of the function setContentProtection(true).

Environment details


MacOs Monterey v12.3.1
jitsi-meet-electron: v2023.7.2
Screen Shot 2023-08-11 at 08 15 34

@saghul
Copy link
Member

saghul commented Aug 11, 2023

This used to work (sigh). Something must have changed in a recent Electron update...

@csett86 csett86 added the macOS Issues affecting macOS label Jan 28, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 15, 2025
@saghul
Copy link
Member

saghul commented Feb 15, 2025

Closing since this is an upstream Electron bug. Depending on the capture backend it simply doesn't work.

@saghul saghul closed this as not planned Won't fix, can't repro, duplicate, stale Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
macOS Issues affecting macOS stale
Projects
None yet
Development

No branches or pull requests

3 participants