-
Notifications
You must be signed in to change notification settings - Fork 15k
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
fix: draggable regions on MAS #37466
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terrifying, I love it. One non-blocking nit on the dcheck
Release Notes Persisted
|
I have automatically backported this PR to "23-x-y", please check out #37473 |
I have automatically backported this PR to "24-x-y", please check out #37474 |
Description of Change
This makes draggable regions work on MAS builds again, after they broke in
#35603.
The mas_disable_custom_window_frame.patch patch prevents the Chrome custom frame from being used on MAS, but the new draggable regions impl on macOS requires it, so we need to find another way of getting this behavior without tripping the MAS guards.
Fixes #37414.
Checklist
npm test
passesRelease Notes
Notes: Fixed draggable regions not working in Mac App Store builds.