> 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-6/v6-3/v6-3-6.md). # Version 6.3.6 Changelog (2020-07-29) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## Fixes * Fixed issue where typing in certain text areas in a PDF document causes the screen to flicker * Fixed issue with accented characters in freetext annotations being cut off * Fixed issue where drawing a FreeHand annotation on one page and then another quickly causes an error * Fixed UI bug where exiting full-screen mode causes the lower part of the thumbnails panel to go offscreen * Fixed issue where annotation could not be modified if the Author was missing * Fixed issue where multiple selected annotations from different pages were not moving in the same direction * Fixed issue with widgets not showing the correct formatted value when they have the same name * Fixed issue where in some instances, the Pantool remains selected when switched out --- # 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-6/v6-3/v6-3-6.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.