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: crash on custom printing margins #22164
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.
LGTM, I believe all these validation crash cases are going to be covered in #22049 ?
Release Notes Persisted
|
I was unable to backport this PR to "8-x-y" cleanly; |
I was unable to backport this PR to "7-1-x" cleanly; |
I have automatically backported this PR to "9-x-y", please check out #22185 |
@codebytere has manually backported this PR to "8-x-y", please check out #22186 |
@codebytere has manually backported this PR to "7-1-x", please check out #22187 |
Description of Change
Closes #21167.
Chromium changed their margin key settings such that custom margins should be set as their own dictionary, and without that will fail conversion validation and crash. This fixes that.
cc @zcbenz @deepak1556 @nornagon
Checklist
npm test
passesRelease Notes
Notes: Fixed a crash in
webContents.print()
with custom print margins.