# Book Isle reader menu visibility: distinguish content taps, menu state and button actions

Language: en
Canonical: [Book Isle reader menu visibility: distinguish content taps, menu state and button actions](<https://allluckly.cn/en/guides/nasbook-reader-menu-visibility-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-reader-menu-visibility-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-reader-menu-visibility-check/>)
Published: 2026-11-06T00:00:00+08:00
Modified: 2026-11-06T12:13:22+08:00
Author: Bison

Use a downloaded TXT or EPUB to check opening, hiding and control response after the 1.1.4 update, distinguishing animation waiting from a reproducible fault.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-reader-menu-visibility-check/>), translated on 2026-11-06. Original publication dates, attribution, code and version notes are retained.

Book Isle 1.1.4 publicly describes improvements to reader-menu visibility and button response. Use a downloaded TXT or EPUB whose text already displays normally to check whether a content tap changes the menu and a button tap performs its intended action. Pair each action with its visible state instead of tapping repeatedly into an indescribable result. Toolbars need not look identical across formats or devices, and an update is not a guarantee that every device passes each check.

## Fix one local book and its starting location

Confirm the installed version in app or system information, then open a legitimately available local TXT or EPUB. Record title, chapter heading and a distinctive nearby phrase. Resolve downloads or missing text first rather than calling a loading blank a hidden menu. For the first pass, close extra overlays such as active read-aloud controls and clear any text selection. Record device, system and orientation without copying private book text. Begin only with a stable passage so later changes can be attributed to a tap instead of ongoing loading.

## Record whether the menu is actually visible

Observe the upper and lower reading controls and record menu visible or menu hidden alongside the passage location. Do not infer the entire state from dimming, a status-bar change or one small icon. Devices may use floating or edge-attached bars, so identify currently available return and contents controls without prescribing pixel positions. If a settings panel covers the passage, return to the ordinary menu layer before recording. Name menu, settings subpanel and book content separately so a later cannot close report identifies the right overlay. Observe only; do not simultaneously change font, theme and page-turn mode.

## Test a content tap separately from text selection

Single-tap once near the middle of content, away from links, buttons and selection handles. Wait for visible animation to settle and record whether hidden becomes visible or the reverse. Keep long press, double tap, selection dragging and edge page-turn zones separate. Text should remain readable with no accidental chapter or phrase change. If a page turns instead, record the actual region and result, then try a clearly central content position rather than repeatedly striking the same edge. When starting with an open menu, label that state explicitly instead of merging different starting states into taps do nothing. One action at a time gives reproducible conditions.

## Judge button taps by their own task

Once the menu is stably visible, choose one control that does not alter book content, such as contents. Tap once, inspect its list and return to the passage. A control tap must be judged by its own task rather than automatically treated as a content tap. A changing menu alone does not prove failure; check whether the target list opened. If a previous rapid tap occurred during animation, wait for stability and try once again instead of reporting temporary waiting as permanent failure. Do not test deletion or metadata editing. Record control name, prior state and destination, using visible wording where needed rather than only the little upper-right button.

## Identify the layer again after leaving a subpanel

After opening settings or contents, use that interface’s available return or close action to reach the passage, then observe the ordinary menu. Some paths may dismiss it and others retain it; do not assume identical behaviour everywhere. What matters is a coherent present state and next action. A chapter chosen in contents deliberately changes the passage; record it separately rather than calling it a menu jump. Start with one subpanel route before adding another. If a contents heading remains visible, you have not yet reached the reading page; tapping its blank area does not test content-menu hiding. Identify the navigation layer instead of tapping repeatedly.

## Inspect hidden state for stray controls

After hiding the menu, look for an isolated return icon, duplicate top bar or button obstructing text, then make one normal tap in clear content. Do not test an uncertain edge icon by activating it; capture its position in a screenshot or short note first. Distinguish system status indicators and navigation-gesture hints from reader buttons. If only a visual remnant remains while reading works, report that distinction rather than declaring the book unreadable. Bar styles may differ, but visible elements in hidden state should have identifiable roles. Record uncertainty rather than guessing that a similar icon belongs to a previous page.

## Recheck anomalies with a short stable sequence

For a reproducible anomaly, reopen the same book from the shelf, confirm the original chapter area and perform only show, hide, contents and return. Let each state settle and record its actual result instead of tapping a dozen times and retaining only the final screenshot. Keep the first record when comparing a known-good local TXT, separating file factors from reader routes. If only one format is affected, scope the report to it rather than every reader. Do not erase reproduction conditions by deleting the book or reinstalling. If needed, retain device, system, version, action sequence and anonymised images, limiting private text to a locating phrase.

## Finish at a recoverable reading location

Finish at the chosen chapter with readable text and an identified menu state. Leave through the normal return action and reopen once, verifying title and phrase have not been confused with another book. Keep a short checklist of starting state, content-tap result, button destination, return result and anomaly reproducibility. A normal outcome applies to this book and environment, not all systems and formats. Repeat the small workflow after a later update instead of judging speed from memory. Retain original notes and correction dates; concrete state transitions should explain responsiveness beyond a general feeling of improvement.

## Related tutorials and sources

[Book Isle getting started: import your first EPUB and resume reading](<https://allluckly.cn/en/guides/nasbook-getting-started/>); [Book Isle between phone and iPad: two layouts for the same chapter](<https://allluckly.cn/en/guides/nasbook-phone-tablet-layout/>).

Sources checked on 6 November 2026: the [official Book Isle App Store listing](<https://apps.apple.com/cn/app/id6766198898>) and [Apple Lookup](<https://itunes.apple.com/lookup?id=6766198898&country=cn>) show version 1.1.4, requiring iOS / iPadOS 15.6 or later. This workflow uses local reading, search, bookmarks and notes for manual checking. Readers record the samples and conclusions; automatic file repair or identical interfaces across all readers is not assumed. Confirm available controls against the installed version and file type. The exercise does not claim step-by-step device testing in this batch.