[Bug]: Unable to detect the screen after Mission Control usage

[vmatyagin]

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 bug report that matches the one I want to file, without success.

Electron Version

29.1.4

What operating system are you using?

macOS

Operating System Version

macOS, 14.2.1 (23C71)

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

No response

Expected Behavior

Bounds are correct after moving a window to another display from mission control.

Actual Behavior

Bounds are incorrect after moving a window to another display from mission control.

Testcase Gist URL

https://gist.github.com/VMatyagin/2e453a22a0ca3e355350872bbfa96bca

Additional Information

The dimensions can only be calculated after move event on the observed component

Actually, I wrote a native module as a workaround fix, but in this case the window opens with correct bounds, but the content width is still the same and changes only after the show event even with disabled backgroundThrottling. It seems setBounds only applies after show event

electron-issue.mp4