> 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-10/v10-6/v10-6-1.md). # Version 10.6.1 Changelog (2024-03-11) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## WebViewer Core ### Fixes Annotations * Fixed an issue with the snipping tool preventing the proper rotation from being read. * Fixed an issue where not all rotation information was serialized the first time the annotation was exported. Content Edit * Increased link detection accuracy a bit. * Fixed an issue where if full API is enabled and a document is loaded through URL, the Content Edit mode might crash the page. Template Generation * Fixed an issue where office templates downloaded as PDF did not include the filled data. Forms * Fixed an issue with Form documents utilizing Adobe global from not populating correctly. Security * Fixed an issue with input validation of TextWidget input values. General * Fixed an issue with the snipping tool to work with page and view rotations. * Fixed an issue of applying CSS transform scale to the WebViewer container. ## WebViewer UI ### Fixes General * Fixed the issue that made the download button unavailable in read-only mode. * Fixed an issue with the scale overlay modal where input is lost after changing the value once. * Fixed an issue where users could comment while multi-selecting annotations in read-only mode. --- # 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-10/v10-6/v10-6-1.md?ask=&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.