> 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-3/v3-0-1.md). # Version 3.0.1 Changelog (2017-06-29) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ### PDFNetJS Updates * Added Document.getOfficeResources to get the resources used by a given page in an office document * Fix issue where the PDF worker would be unnecessarily loaded when loading an office file * Fix issue with error handling where some errors could be misreported as license errors ### WebViewer HTML5 Updates * Added `Tools.Tool.ENABLE_AUTO_SWITCH` to disable automatic switching of the pan and text select tools * Fixed issue where WebViewer.js would warn about certain options not being valid even though they actually were * Fixed issue in FreeText annotations with auto font size and a large height the initial font size would be very large * Fixed issue with potential rerendering of pages when the cache size is small * Fixed issue where the "Current Page" print option wasn't localizable * Fixed issue where checkboxes and radio buttons weren't visible in the latest Firefox version * Fixed issue with the annotation edit tool where the annotation canvas could be incorrectly translated when in viewport rendering mode * Fixed issue where search could fail on some older XOD files --- # 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-3/v3-0-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.