# 2.25.0

## UI changes for ePUB experience, new touch based interactions, bug fixes

| Version      | 2.25.0     |
| ------------ | ---------- |
| Release Date | 2018-08-30 |

## Key features <a href="#id-20180830engage2.25.0uichangesforepubexperience-newtouchbasedinteractions-bugfixes-keyfeatures" id="id-20180830engage2.25.0uichangesforepubexperience-newtouchbasedinteractions-bugfixes-keyfeatures"></a>

This release introduces UI changes that make the EPUB experience more user friendly, new touch based interactions for mobile and tablet devices, and a few defect fixes.

## Details <a href="#id-20180830engage2.25.0uichangesforepubexperience-newtouchbasedinteractions-bugfixes-details" id="id-20180830engage2.25.0uichangesforepubexperience-newtouchbasedinteractions-bugfixes-details"></a>

### EPUB experience

* Fixes an issue where 100px of dead space are padded below the EPUB reader in the Engage window.
* UI changes direct users attempting to upload an EPUB to work through Unizin Services to deliver that content in Engage to their students.

### Touch-based interactions

* New touch based interactions. We have redesigned Engage's touch interactions for mobile and tablet devices. Engage now uses more modern libraries and has improved performance.

### Miscellaneous fixes

* Notifications can now be dismissed by the user (rather than just waiting for them to disappear).
* Fixes issue in All notes view where question counts may be inaccurate
* IE 11 user interface fixes: user menu, upload experience

## Known Issues

None.


---

# Agent Instructions: 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:

```
GET https://resources.unizin.org/products/content/unizin-engage/release-notes/2018-08-30-engage-2.25.0-ui-changes-for-epub-experience-new-touch-based-interactions-bug-fixes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.