[Bug]: transition between minimized / maximized frameless window used to be smooth in 16.0.8; is no longer smooth in 17.0.1

[DogFoxX]

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

17.1.0

What operating system are you using?

Windows

Operating System Version

Windows 10 21H2

What arch are you using?

x64

Last Known Working Electron version

16.0.8

Expected Behavior

Frameless window maximizing and minimizing should be smooth

Actual Behavior

I'm not sure on which version of electron this started, but I updated from v16.0.8 to 17.0.1.
I'm using a frameless window with custom minimize, maximize and close buttons.
When the window is maximized or minimized, there is no longer a smooth transition.

Testcase Gist URL

No response

Additional Information

No response

[ckerr]

Thanks for reporting this and helping to make Electron better!

Please use Electron Fiddle to create a standalone (no external dependencies) testcase and publish it as a gist, then link to it here.

• Even if you have a code snippet or a git repository that show the testcase, please put it in a gist. This lets maintainers triage issues more effectively. It also ensures that we're testing the exact same issue that you're seeing!

• Please avoid external dependencies in the test. The Electron team is small and generally doesn't have enough bandwidth to triage third-party code. Also, standalone tests are easier to adapt into regression tests.

• If the bug you've found can be tested with a pass / fail test, please make the testcase exit 0 on success or nonzero on failure. The lets Electron's issue bot see what releases are affected by the bug.

I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to the gist in a followup comment.

Thanks in advance! Your help is appreciated.

[t57ser]

Seems like the same as: #32993

[mlaurencin]

I agree, this looks like a duplicate of #32993. You may want to subscribe there for updates.

Because we treat our issues list as the project team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.