> 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-8/v8-4/v8-4-1.md). # Version 8.4.1 Changelog (2022-04-07) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## WebViewer Core ### Fixes * Fixed issue with searching up and down when using single search API * Fixed issue with dragging form fields across pages * Fixed rotation issue for WebViewer Server * Fixed issue where the deprecated `office2PDFbuffer` API wasn't working * Fixed issue where a cross origin document loaded with WebViewer Server will fail * Fixed issue where newly created signature is not center-aligned ## WebViewer UI ### Fixes * Fixed issue where multi-tab mode wouldn't save page alterations * Fixed issue where signature tool style popup is closed when hovering over text * Fixed issue where dark mode is not supported for redaction panel * Fixed issue where the `Label Text` functionality wasn't able to be disabled * Fixed issue where hitting Enter at 3D annotations ADD dialog resets the 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-8/v8-4/v8-4-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.