> 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-5/v10-5-1.md). # Version 10.5.1 Changelog (2023-11-09) World's #1 PDF SDK Library for Web, Mobile, Server, Desktop ## WebViewer Core ### New * Added shortcut support for content edit mode decorators (Bold, Italic, Underline) * Added client-side support for XLSM and XLT files * Added a PDF edit event `undoRedoStatusChanged` under namespace `ContentEdit` * Added optimizations for Salesforce when using the `optimize-for-prod` script ### Fixes * Fixed an issue where watermarks could not be added to image documents * Fixed issue where some files with portfolio content, could not be opened in Adobe after being downloaded from WebViewer * Fixed issue where users could not input text when in content edit mode using Android devices * Fixed issue where content edit was not working in iOS devices * Various fixes issues with drawing annotations when using VirtualDisplayMode ## WebViewer UI ### New * Added a new feature mode in the UI `Feature.SideBySideView`, which toggles the side-by-side view in the view controls dropdown. * Added order improvements for portfolios ### Fixes * Fix issue where the display author was not being saved correctly when downloading a DOCX file * Fixed an issue where the autolinker would detect URLs in auto replies in the notes panel, such as when changing a note's state * Reverted a breaking change where `Feature.MultiViewerMode` was removed in the previous release. This feature is now available again. --- # 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-10/v10-5/v10-5-1.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.