> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/changelogs/version-12/v12-0-1.md).

# Version 12.0.1 Changelog (2026-07-20)

## WebViewer Core

The WebViewer Core changelog covers low-level API, engine, and infrastructure changes that power the Web SDK.

### Fixes

#### DOCX Editor

* Fixed rendering issue in specific scenarios after replacing selected text.

#### Spreadsheet Editor

* Fixed an issue where undoing or redoing a cell value that was referenced in a formula would not update dependent charts correctly.

## WebViewer UI

The WebViewer UI changelog covers user interface, customization, and workflow enhancements available through the Web SDK.

### Fixes

#### Multi-instance

* Fixed several issues where multiple WebComponent instances on the same page could interfere with each other, including cross-instance React reconciliation crashes on dispose/re-render, `UI.dispose()` corrupting other instances or clearing more of the UI than intended, `UI.setTheme()` toggling the wrong instance's theme, and the `Open file` picker loading a document into the wrong instance.
* Fixed a crash that occurred when clicking an annotation in the Notes panel of one WebViewer instance while another instance was also mounted on the same page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/web/changelogs/version-12/v12-0-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.