4.3.0-rc3

[demiankatz]

This is the third release candidate for 4.3.0, fixing a bug introduced in RC2 (#1627) and updating further dependencies.

This RC also includes some further adjustments to the release workflow in an effort to get NPM publishing working again; as of this writing, it is still not functional, so this RC has been manually published.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
universalviewer	Ready	Preview, Comment	Jan 12, 2026 9:42am
universalviewer.dev	Ready	Preview, Comment	Jan 12, 2026 9:42am

[vercel]

@demiankatz is attempting to deploy a commit to the BL UV team Team on Vercel.

A member of the Team first needs to authorize it.

[LanieOkorodudu]

I've been testing RC3 over the past 2 days on both desktop and mobile. I also checked keyboard navigation and screen reader support (NVDA). Everything is working as expected, and A/V loads correctly.
Thank you @demiankatz and the rest of the team for all the work that went into RC3!

I wanted to share a small thought regarding some of the example manifest that don't currently load. It might be worth considering either removing these from the example page or replacing them with manifests that load successfully. From a testing perspective, it can be a bit confusing when some examples don't load, even though the issue appears to be with the manifests themselves rather that the viewer.
I'm also thinking about the experience for the new users, if they try these examples and run into issues, they might assume the viewer is at fault, simply because it's not obvious that the manifest are the source of the problem.
This isn't a blocker by any means, and it may be better handled as a separate issue, but I wanted to share the thought and get your opinion and the rest of team.

For reference: These are the manifest that are currently unable to load:
Florence Nightingale(audio):

• https://wellcomelibrary.org/iiif/b17307922/manifest

British Library

• https://api.bl.uk/metadata/iiif/ark:/81055/vdc_100022545251.0x000002/manifest.json

National Library of Wales

• http://dams.llgc.org.uk/iiif/2.0/4389767/manifest.json
• http://dams.llgc.org.uk/iiif/2.0/1123257/manifest.json
• http://dams.llgc.org.uk/iiif/archive/3975658/fonds.json

Bodleian

• http://iiif.bodleian.ox.ac.uk/examples/mushaf4.json
• http://iiif.bodleian.ox.ac.uk/iiif/manifest/60834383-7146-41ab-bfe1-48ee97bc04be.json

National Gallery of Art

• http://media.nga.gov/public/manifests/nga_highlights.json

Test

• http://tomcrane.github.io/scratch/manifests/top-to-bottom.json
• http://tomcrane.github.io/scratch/manifests/bottom-to-top.json
• https://heaney0.ugent.be/custom_manifests/B_OB_MS685.json

SlideAtlas

• https://slideatlas-test-manifests.netlify.app/collection/girder/index.json

[demiankatz]

@LanieOkorodudu, I am definitely in favor of cleaning up the examples. They are defined here:

https://github.com/UniversalViewer/universalviewer/blob/9fc8e64aeaec2da744d5dec1a367207aad662ba6/src/iiif-collection.json

As a starting point, maybe it's worth opening a PR to simply remove any manifests that are broken links or obvious tests (rather than real-world examples).

For the real-world examples that don't work (like the NLW ones you mention), maybe we need to talk to stakeholders and figure out why they are broken. Is there something wrong with the manifests, or did they work at some point in the past and got broken by some UV issue that needs investigation?