fix: setContentProtection affects BrowserWindow frame #31768
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Closes #31735.
If the layered property is set before setting the affinity, the window frame disappears in some cases. Switching the order solves the issue - I believe this is a Windows bug.
cc @KazuyaHayashi
Checklist
npm test
passesRelease Notes
Notes: Fixed window frame glitch when calling
setContentProtection
.