> 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-6/v8-6-1.md). # Version 8.6.1 Changelog (2022-06-30) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## WebViewer Core ### Fixes * Fixed bug with slow annotation rendering at high zoom levels * Fixed issue with disappearing signature on zoom in Chrome * Fixed issue with generated appearances for some formatted fields * Fixed bug where the date string could not be cleared for date fields * Fixed failure when manually importing annotations with appearances on a WebViewer Server document with no appearances * Fixed issue with missing bullet glyphs when converting DOCX to PDF * Fixed issue where text would be trimmer too much in smaller text fields * Fixed an issue where DatePicker is fully/partially hidden when virtual keyboard was open * Fixed issue with overlapping text when rotating a justified FreeText annotation * Fixed issue where an error would be thrown if the layout was changed and virtual render mode was enabled when working with a local XOD file * Fixed XOD rendering issue when transparency group opacity is 0 * Fixed TIF files not loading properly with WebViewer Server * Fixed issue where Polylines and Polygons were being deleted prematurely ## WebViewer UI ### Fixes * Updated Korean translations * Fixed selection issue with signature popup --- # 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-6/v8-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.