[BUG]: Safari 16.5+ and Chrome 116 not supported

[HeadCookie]

Describe the bug
@pdf-viewer/react incorrectly displays a "Browser not supported" error on environments that meet the requirements stated in both the error message and official documentation.

Testing via BrowserStack confirms failures on MacOS Ventura with Safari 16.5.1, MacOS Sonoma with Safari 17.3, and Windows 11 with Chrome 116.0.5845.96. These failures contradict the on-screen error claiming support for Safari 16.5+ and Chrome 110+, as well as developer documentation citing Chrome 115+. I was able to confirm successful rendering on newer versions starting from Windows 11 with Chrome 128 and MacOS Sequoia with Safari 18.4.

To Reproduce
Steps to reproduce the behavior:

1. Open any PDF in Safari 16.5.1, 17.3
2. Error message appears saying browser not supported

Expected behavior
Either support the Safari 16.5.1 and Chrome 116 or update the error message and dev docs browser support list to reflect which browsers are actually supported.

Screenshots

Desktop (please complete the following information):

• OS: MacOS Ventura/Sonoma and Windows 11
• Safari 16.5.1 & 17.3
• Chrome 116 & 117
• @pdf-viewer/react 1.13.0 and pdfjs-dist 4.10.38

[david-reactpdf]

@HeadCookie

Thanks for reporting this, we’re aware of the issue and currently looking into it. I’ll keep this thread updated once we have a resolution or workaround.

[HeadCookie]

@david-reactpdf Thank you for the swift reply. I looked into it a bit, and it seems the issue is likely related to the use of the main build of pdf-js dist. The documentation mentions using the legacy build that has the polyfills necessary to support older browser versions.

[david-reactpdf]

@HeadCookie

Thanks for the helpful insight. We’ve done some testing and can confirm that using pdfjs version 4.0.x allows React PDF to work on older versions of Safari (e.g., <17.4). However, there are some limitations, for example, text search highlights do not display even though the search navigation still works.

If highlighting isn’t essential, switching to pdfjs 4.0.x might be a suitable temporary workaround.

We’re actively working on a proper fix to support older Safari versions while maintaining full functionality. Will keep this thread updated as we make progress. Thanks again for your patience.