Report Issues / Request Features
Found a problem or have an idea for Ambra? First check existing GitHub issues for a matching report.
- Report an issue.
- Request a feature.
- Without a GitHub account, email AmbraEPUB@outlook.com.
Both GitHub links open the repository’s new-issue chooser. Use a suitable template if one is offered, or describe the issue or request in a new report. GitHub issues are public.
Make a problem reproducible
Include:
- What happened and what you expected, with short, numbered steps to reproduce it.
- Ambra version, Chrome version, and operating system. Find Ambra’s version in Help & About, available from the question-mark control in the Library or reader toolbar, or from the reader’s Book details footer.
- Reading layout: reflowable or fixed-layout, pagination or scrolling, one page or a spread, and any relevant text, theme, or window-size settings.
- Scope: whether it affects one book or several, and whether it happens every time. For navigation problems, identify a chapter or location without exposing private text.
- A minimal sample if needed: a small EPUB you are legally allowed to share, using public-domain, your own, or redacted content that still reproduces the problem. A redacted screenshot may help too. You do not need to upload a whole book.
For a feature request, explain the reading task you want to accomplish, what makes it difficult now, and the result you would find useful.
Share diagnostics carefully
Help & About offers a copy control for environment information or, when opened in the reader, reader diagnostics. Diagnostics are not sent automatically. They describe recent activity and can contain book details, paths, reading positions, and error information; the recent-event history resets when the reader reloads.
Do not post private books, notes, credentials, or full diagnostics without reviewing them. Remove personal information, private passages, sensitive filenames or paths, and anything you do not have permission to share. Review screenshots and annotation exports too. The same care applies when sending email; do not assume email is a safe place for an unreviewed book or report.
For a layout or source problem, the read-only EPUB Inspector can help identify the affected file. Share only the smallest lawful, reviewed excerpt needed to explain it.
See the official privacy policy for privacy details, or the MIT-licensed source repository for development context.