> 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-0/v10-0-2.md). # Version 10.0.2 Changelog (2024-03-11) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## WebViewer Core ### Fixes General * Added a security measure to prompt the user before redirecting to a URL that can be embedded in the XFDF of the PDF. * Fixed the bug where `Document#getFilename()` returns an empty string for loading non-PDF files with `loadAsPDF: true`. * Fixed an issue where disabling enter keypress on a FreeText annotation would mess up editing mode. * Fixed an issue where enabling enter keypress would not work. * Fixed an issue where global editor settings were changed unexpectedly. * Fixed free text annotations incorrectly rendering tab stops. * Fixed free text annotations incorrectly measuring tab stops. Security * Fixed an issue with input validation of `TextWidget` input values. ## WebViewer UI ### Fixes General * Sanitized attached SVG files to remove malicious scripts. * Fixed `SYNC_UNMATCHED` scroll syncing for `MultiViewerMode` when page counts are radically different on both sides. Forms * Prevented the creation of fields with a blank name when using the form builder. --- # 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-0/v10-0-2.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.