> 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-11/v11-1/v11-1-1.md).

# Version 11.1.1 Changelog (2024-12-09)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

## WebViewer Core

### New

General

* Added optimization to load pages with annotations and defer pages with many links.

Office Editor

* Added a timed event for grouping undo and redo actions while editing content.
* Added support for loading .doc format in the Office Editor.
* Improved tabbing behavior.

###

Fixes

General

* Fixed memory leak caused by threaded WebAssembly (Wasm).
* Fixed issue with Embedded JavaScript XSS protection for delete actions.
* Fixed issue where forms would disappear in virtual display mode when navigating away and back.

Content Edit

* Fixed issue with `ContentBox.stopContentEditing`, preventing changes from being saved.

Office Editor

* Fixed inconsistent behavior of undo/redo buttons and associated hotkeys.
* Fixed grouped continuation for insert, delete, and backspace undo/redo events.

Annotations

* Fixed issue where Free Hand Highlight annotations did not support the "multiply" blend mode.
* Fixed incorrect appearance when exporting Arc annotations with exportAnnotations.

## WebViewer UI

### Fixes

General

* Fixed an issue where hotkeys could be triggered outside of WebViewer.

Annotation

* Fixed issue where horizontal alignment was not applied to new redactions in the Redaction Search Panel's "Mark All" button.
* Fixed issue where annotation popups caused unintended scrolling (up or left).

Customize UI

* Fixed issue with lingering visual artifacts after button hover styles were applied.

Stamps

* Fixed issue where Stamp preview did not resize when zoom was adjusted.


---

# 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-11/v11-1/v11-1-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.