> 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-3.md). # Version 6.3.3 Changelog (2020-06-19) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop * Fixed issue where the datalist element wasn't used in Safari versions that support it * Fixed several issues with the overrideSelection property behavior on tools * Fixed issue where searching did not work in some XOD files * Fixed issue with downloading some FreeText annotations without a defined appearance and style * Fixed issue where signature appearance wasn't displayed for older XOD files * Fixed issue that would occur when printing some XOD files * Fixed issue where calling CoreControls.disableEmbeddedJavaScript threw an error for documents that have embedded JS * Fixed issue where the aspect ratio of thumbnails wasn't preserved in some cases * Fixed issue where it sometimes scrolled to incorrect row when clicking on thumbnail in thumbnail panel --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.apryse.com/web/changelogs/version-6/v6-3/v6-3-3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.