-
|
I have a question regarding react-pdf v10. I figured out that a Safari Browser v17 crashes, while v18 doesn't. I read that comment below in the release notes. Does that really mean only the latest version of all modern browsers? Because I wouldn't consider Safari v17 as old. And I don't understand why you would drop the support for it. It's just one version behind. How would that work on scale? You cannot know which browser version customers are using. For every old versions, yeah, I get that. But one version behind the newest?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hey! Yeah, wording isn't exactly the most fortunate on that one. They are technically older than something else out there but can't be considered old 😅 Any suggestions? My decision here isn't really mine - Mozilla's team behind PDF.js is widely using bleeding edge language features. At the same time, their legacy build offers worse performance and is simply bigger, with "normal" build already being enormous. That's why I'm suggesting to process PDF.js on your own with your bundler to increase backwards compatibility. Alternatively, you may try your luck with aliases to rewrite pdfjs-dist/* to pdfjs-dist/legacy/*. |
Beta Was this translation helpful? Give feedback.
Hey! Yeah, wording isn't exactly the most fortunate on that one. They are technically older than something else out there but can't be considered old 😅 Any suggestions?
My decision here isn't really mine - Mozilla's team behind PDF.js is widely using bleeding edge language features.
At the same time, their legacy build offers worse performance and is simply bigger, with "normal" build already being enormous.
That's why I'm suggesting to process PDF.js on your own with your bundler to increase backwards compatibility.
Alternatively, you may try your luck with aliases to rewrite pdfjs-dist/* to pdfjs-dist/legacy/*.