[Bug]: setContentProtection affects an application window behavior

[KazuyaHayashi]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

15.2.0

What operating system are you using?

Windows

Operating System Version

Windows 10 version 20H2

What arch are you using?

x64

Last Known Working Electron version

15.1.2

Expected Behavior

Apply setContentProtection function without any effects on the application window behavior on browser-window-created event.

Actual Behavior

When setContentProtection function is called on browser-window-created event, the application window form will changed when the focus is backed. The value of the argument of setContentProtection has no effect on the result.

Testcase Gist URL

https://gist.github.com/KazuyaHayashi/33372ae657dde602e68fdb50aabafa31

Additional Information

When I call setContentProtection just after creating BrowserWindow, this issue does not happen. But I want to set contents protection on each windows which are created by new-window event. Therefor, I have called setContentProtection function on browser-window-created event.

[deermichel]

Reproduced on Win10 2004, introduced by #31340. Doesn't occur with setOpacity though 🤔

[deermichel]

Actually this serves as a temporary workaround:

app.on('browser-window-created', function(e, w) {
  w.setOpacity(1.0)
  w.setContentProtection(true)
})

[deermichel]

Fixed and confirmed to work in 16.0.0.