> 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-7/v10-7-2.md).

# Version 10.7.2 Changelog (2024-02-21)

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

## WebViewer Core

### Fixes

* Fixed an issue with Highlight Annotations that broke annotation drawing after rotating a page.
* Fixed an issue where the app entered a bad state after switching out of the marquee zoom tool.
* Fixed an issue where not all rotation information was serialized the first time the annotation was exported.
* Fixed an issue with WebViewer not focusing on the text cursor when typing.
* Fixed an issue that prevented the onclick event from firing when tapping on an unsigned signature widget on mobile devices.
* Fixed an issue with the snipping tool that prevented the proper rotation from being read.

## WebViewer UI

### Fixes

* Fixed an issue with the new panel APIs that caused a rendering error when modifying the location of the modular panels.
* Fixed an issue with browser reload on hash change event in WebViewer WebComponent.


---

# 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-7/v10-7-2.md?ask=<question>&goal=<endgoal>
```

`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.
