---
title: "1.26 release notes"
canonical_url: "https://www.nutrient.io/guides/web/release-notes/1-26/"
md_url: "https://www.nutrient.io/guides/web/release-notes/1-26.md"
last_updated: "2026-11-19T00:00:00.000Z"
description: "Nutrient Web SDK 1.26 can draw form fields and annotations in document order, reports changes that Document Engine refuses, and bundles React 19."
---

Nutrient Web SDK 1.26 adds an option to draw form fields and annotations in the order the document lists them. It also adds the `sync.refused` event, which reports changes that Document Engine permanently refuses.

This release also includes these changes:

- Toolbar color buttons include the selected color in their accessible name.

- The SDK bundles React 19.

For a complete list of changes and fixes, refer to the [changelog](https://www.nutrient.io/guides/web/changelog.md#1.26.0).

### Form fields and annotations in document order

By default, the SDK draws form fields above annotations such as shapes, ink, stamps, and notes. An annotation placed over a form field appears below it.

To draw form fields and annotations in the order the document lists them, set `forceRenderWidgetsInAnnotationsOrder` to `true` in the view state:

```js

NutrientViewer.load({
  initialViewState: new NutrientViewer.ViewState({
    forceRenderWidgetsInAnnotationsOrder: true,
  }),
});

```

The SDK then draws each annotation above the form fields that precede it in the document, and the annotation receives clicks where they overlap. New annotations and form fields come last, so they appear on top.

The following limits apply:

- Text markup annotations, such as highlights and underlines, stay below all other annotations. Links, ink signatures, and image signatures stay on top.

- The tab order doesn’t change. When an annotation completely covers a form field, users can reach the field only with the keyboard. The field appears on top while it has focus.

- Changing the tab order with `instance.setPageTabOrder()` can also change the drawing order, because it reorders the page’s annotation list.

- A comparator set with `instance.setAnnotationRenderingOrderComparator()` takes precedence over the option, and form fields stay on top.

In server-backed mode, the following also applies:

- Annotations from an uploaded PDF retain document order only with Document Engine 1.21.0 or later, which isn’t released yet. With an older version, they stay below form fields, and new annotations still appear on top.

- With Document Engine 1.21.0 or later, editing an annotation or form field from the uploaded PDF moves it to the top on the next load. Image annotations, stamp annotations, and form fields that show an image retain their place.

- An exported PDF lists new form fields before new annotations. A form field created after an annotation appears below it in the exported PDF.

For more information, refer to the [annotation customization](https://www.nutrient.io/guides/web/annotations/custom-rendered-annotations.md#drawing-form-fields-in-document-order) guide and the [`forceRenderWidgetsInAnnotationsOrder`](https://www.nutrient.io/api/web/classes/NutrientViewer.ViewState.html#forcerenderwidgetsinannotationsorder) API reference.

### Changes refused by Document Engine

Document Engine can permanently refuse a change — for example, because of collaboration permissions. Before 1.26, an annotation or comment retained a refused change until the document reloaded. The annotation or comment now returns to the version that Document Engine holds, and the SDK restores it after a refused deletion.

When the SDK reverts a refused update, it emits `annotations.update` or `comments.update`, as it does for another user’s change. When it restores an annotation or comment after a refused deletion, it emits `annotations.create` or `comments.create`. If a listener for these events writes changes back, it shouldn’t reapply the refused change.

The SDK also emits the new `sync.refused` event once for each refused change, including changes saved automatically. Use the event to tell users that a change wasn’t saved:

```js

instance.addEventListener("sync.refused", (refusal) => {
  console.warn("A change could not be saved:", refusal.error.message);
});

```

The listener receives an object with the following properties:

- `error` — An `Error` whose message can include the reason Document Engine gave. The message isn’t a stable code.

- `affectedObject` — The object or value that the refused change tried to save. The restored object can differ from it.

- `modificationType` — The refused operation, which is `"CREATED"`, `"UPDATED"`, or `"DELETED"`.

The event doesn’t report temporary network failures, conflicts, or retries, and the SDK never emits it in standalone mode. The `instance.save()` and `instance.ensureChangesSaved()` methods still report the refusal. The `instance.hasUnsavedChanges()` method reports pending work, not past refusals.

For more information, refer to the [autosave](https://www.nutrient.io/guides/web/features/saving.md) guide and the [`sync.refused`](https://www.nutrient.io/api/web/enums/NutrientViewer.EventName.html#sync_refused) API reference.

### Toolbar color buttons

Toolbar color buttons now include the selected color in their accessible name. For example, screen readers announce “Color Blue” or “Fill Color None.”

Tests that look for these buttons by their exact name, such as “Color” or “Font Color,” no longer find them. Match the start of the name instead:

```js

// Before 1.26, the exact name matched.
getByRole("button", { name: "Color", exact: true });

// The name now ends with the selected color, so match its start.
getByRole("button", { name: /^Color/ });

```

The color picker now closes when a user selects a custom color, as it does for preset colors.

For more information, refer to the [accessibility](https://www.nutrient.io/guides/web/viewer/accessibility.md) guide.

### React 19

The SDK now bundles React 19 instead of React 18. The SDK uses its own copy of React, so the public API is unchanged, and applications don’t require changes.

This release supports Document Engine 1.5.6 or later. Specific features in server-backed mode require newer versions:

- **Document Engine 1.16.0 or later** — `SearchType.WORD_BASED`, PDF exports without password protection, and removing annotation notes after an XML Forms Data Format (XFDF) roundtrip.

- **Document Engine 1.18.0 or later** — Document-defined annotation tab order, `Annotation.createdBy`, `overprintPreview`, and `blackRendering`.

- **Document Engine 1.20.0 or later** — Viewing and toggling PDF layers. This version also fixes text selection highlights that skip spaces between words in certain PDFs after optical character recognition (OCR).

- **Document Engine 1.21.0 or later** — Document order for annotations from an uploaded PDF when `forceRenderWidgetsInAnnotationsOrder` is `true`. This version isn’t released yet.

Document Engine ignores compound measurements, which work only in standalone mode.

For version requirements, refer to the [Web SDK and Document Engine compatibility requirements](https://www.nutrient.io/guides/document-engine/viewer/client-integration/web.md#version-compatibility) guide.

For the previous release, refer to the [Web SDK 1.25 release notes](https://www.nutrient.io/guides/web/release-notes/1-25.md).
---

## Related pages

- [1 0](/guides/web/release-notes/1-0.md)
- [1 1](/guides/web/release-notes/1-1.md)
- [1 10](/guides/web/release-notes/1-10.md)
- [1 11](/guides/web/release-notes/1-11.md)
- [1 12](/guides/web/release-notes/1-12.md)
- [1 13 1](/guides/web/release-notes/1-13-1.md)
- [1 13](/guides/web/release-notes/1-13.md)
- [1 14](/guides/web/release-notes/1-14.md)
- [1 15](/guides/web/release-notes/1-15.md)
- [1 16](/guides/web/release-notes/1-16.md)
- [1 17](/guides/web/release-notes/1-17.md)
- [1 18](/guides/web/release-notes/1-18.md)
- [1 19](/guides/web/release-notes/1-19.md)
- [1 2](/guides/web/release-notes/1-2.md)
- [1 20](/guides/web/release-notes/1-20.md)
- [1 21](/guides/web/release-notes/1-21.md)
- [1 22](/guides/web/release-notes/1-22.md)
- [1 23](/guides/web/release-notes/1-23.md)
- [1 24](/guides/web/release-notes/1-24.md)
- [1 25](/guides/web/release-notes/1-25.md)
- [1 3](/guides/web/release-notes/1-3.md)
- [1 4](/guides/web/release-notes/1-4.md)
- [1 5](/guides/web/release-notes/1-5.md)
- [1 6](/guides/web/release-notes/1-6.md)
- [1 7](/guides/web/release-notes/1-7.md)
- [1 8](/guides/web/release-notes/1-8.md)
- [1 9](/guides/web/release-notes/1-9.md)
- [2017 3](/guides/web/release-notes/2017-3.md)
- [2017 6](/guides/web/release-notes/2017-6.md)
- [Update your PSPDFKit for Web to version 2017.7](/guides/web/release-notes/2017-7.md)
- [Upgrade annotations in PSPDFKit Web 2017.8](/guides/web/release-notes/2017-8.md)
- [Explore new features in PSPDFKit for Web 2017.9](/guides/web/release-notes/2017-9.md)
- [New features in the 2018.1 migration guide](/guides/web/release-notes/2018-1.md)
- [PSPDFKit for Web 2018.2 migration insights](/guides/web/release-notes/2018-2.md)
- [Discover the new features in PSPDFKit for Web 2018.3](/guides/web/release-notes/2018-3.md)
- [Explore PSPDFKit for Web 2018.4 features](/guides/web/release-notes/2018-4.md)
- [Explore new features in PSPDFKit 2018.5](/guides/web/release-notes/2018-5.md)
- [Explore PSPDFKit for Web 2018.6 enhancements](/guides/web/release-notes/2018-6.md)
- [Explore the new features in PSPDFKit 2018.7](/guides/web/release-notes/2018-7.md)
- [Key updates in PSPDFKit for Web 2019.1](/guides/web/release-notes/2019-1.md)
- [2019 2](/guides/web/release-notes/2019-2.md)
- [PSPDFKit for Web 2019.3 migration highlights](/guides/web/release-notes/2019-3.md)
- [Essential updates in PSPDFKit for Web 2019.4](/guides/web/release-notes/2019-4.md)
- [PSPDFKit for Web 2019.5 migration insights](/guides/web/release-notes/2019-5.md)
- [Key changes in PSPDFKit for Web 2020.1](/guides/web/release-notes/2020-1.md)
- [Seamless migration to PSPDFKit for Web 2020.2](/guides/web/release-notes/2020-2.md)
- [Upgrade to PSPDFKit Web 2020.3 seamlessly](/guides/web/release-notes/2020-3.md)
- [PSPDFKit Web and Server 2020.4 migration update](/guides/web/release-notes/2020-4.md)
- [Unified CRUD API enhancements for easy migration](/guides/web/release-notes/2020-5.md)
- [PSPDFKit Web 2020.6 migration insights](/guides/web/release-notes/2020-6.md)
- [Upgrade to PSPDFKit for Web 2021.1 with ease](/guides/web/release-notes/2021-1.md)
- [Seamlessly migrate to PSPDFKit for Web 2021.2](/guides/web/release-notes/2021-2.md)
- [2021 3](/guides/web/release-notes/2021-3.md)
- [PSPDFKit 2021.4 migration guide for seamless updates](/guides/web/release-notes/2021-4.md)
- [Migration guide for PSPDFKit 2021.5](/guides/web/release-notes/2021-5.md)
- [2021 6](/guides/web/release-notes/2021-6.md)
- [PSPDFKit 2022.1.1 migration changes](/guides/web/release-notes/2022-1.md)
- [Enhancements in PSPDFKit for Web 2022.2](/guides/web/release-notes/2022-2.md)
- [Explore the new features of PSPDFKit for Web 2022.3](/guides/web/release-notes/2022-3.md)
- [PSPDFKit for Web 2022.4 migration overview](/guides/web/release-notes/2022-4.md)
- [Key improvements in PSPDFKit for Web 2022.5](/guides/web/release-notes/2022-5.md)
- [Discover the key updates in PSPDFKit for Web 2023.1](/guides/web/release-notes/2023-1.md)
- [PSPDFKit 2023.2 migration and updates](/guides/web/release-notes/2023-2.md)
- [Key updates in PSPDFKit for Web 2023.3](/guides/web/release-notes/2023-3.md)
- [Explore key updates in PSPDFKit for Web 2023.4](/guides/web/release-notes/2023-4.md)
- [Key updates in PSPDFKit for Web 2023.5](/guides/web/release-notes/2023-5.md)
- [Essential Nutrient Web SDK 2024.1 migration tips](/guides/web/release-notes/2024-1.md)
- [2024 2](/guides/web/release-notes/2024-2.md)
- [2024 3](/guides/web/release-notes/2024-3.md)
- [2024 4](/guides/web/release-notes/2024-4.md)
- [2024 5](/guides/web/release-notes/2024-5.md)
- [2024 7](/guides/web/release-notes/2024-7.md)
- [2024 8](/guides/web/release-notes/2024-8.md)
- [Upgrading Nutrient Web SDK](/guides/web/release-notes/upgrading.md)

