-
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
feat: allow generating accessible pdf with printToPDF
#39563
Conversation
8cde354
to
bfb636e
Compare
@@ -25,7 +25,7 @@ | |||
"mocha": "^10.0.0", | |||
"mocha-junit-reporter": "^1.18.0", | |||
"mocha-multi-reporters": "^1.1.7", | |||
"pdfjs-dist": "^2.2.228", |
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.
This is needed to pull in getMarkInfo()
bfb636e
to
93d50fa
Compare
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.
API LGTM
93d50fa
to
f4358c4
Compare
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.
API LGTM
Release Notes Persisted
|
* feat: allow generating accessible pdf with printToPDF * docs: mark generateTaggedPDF experimental
Description of Change
Refs https://bugs.chromium.org/p/chromium/issues/detail?id=1469961
Refs #39375.
Page.printToPDF
now allows for experimentally generating tagged (accessible) PDFs. We needed to add the property to our implementation in the latest Chromium roll in order to fix compilation errors, but we should surface this new property to developers with a note about its experimental status.Checklist
npm test
passesRelease Notes
Notes: Added a
generateTaggedPDF
option towebContents.printToPDF
to allow generating tagged (accessible) PDFs.