Reading tools and interaction

ManYue chapter comments: distinguish source support from reader controls

Inspect comment controls, chapter-end placement and loading only for an added source that supports comments, without posting or assuming local files have discussions.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

A comment setting does not attach one discussion service to every comic. Chapter comments depend on the added source’s capabilities; local files and ordinary server entries do not automatically gain them. This workflow only inspects existing comments and navigation, without posting.

Choose a source with known comment support

Use an already added authorised source and chapter with known readable comments. Do not import unknown scripts for the exercise or infer app integration from a server website’s discussion feature. Record identity and mark the workflow not applicable if no source supports it.

Check the control in the current context

Inspect the comment setting from the selected chapter, recording scope and initial state. Verify the actual reader entry after enabling it. If absent, recheck source capability and chapter identity before broad changes. A generic switch does not supply a missing source API.

Open comments and verify the chapter

Open the visible entry and check whether it is chapter-specific or work-wide. Read only; avoid send, reply or vote actions. Distinguish loading, errors and an empty result. Discussion spoilers are not evidence of wrong page order. The test requires no communication with other readers.

Compare chapter-end placement conditions

Inspect any mode conditions for chapter-end comments, retaining the original layout before a comparison. If unavailable in continuous reading, use the manual entry. An added discussion region is not a new source image. Identify the actual final artwork and the following interface separately.

Check the result of hiding comments

Disable the relevant display option and inspect both interface changes and normal content/bookmarks. Hiding comments does not delete remote posts or imply account logout. Record observed switch linkage. It is not a file-cleanup or universal cache-removal operation, and reimporting the comic is unnecessary.

Separate source and network failures

Compare body pages and the same source’s comment interface. A comment-only failure may involve different conditions from reading. Another community’s same-title comments are not a valid counterpart. Report source, chapter and visible error with credentials and private links removed.

Recheck when returning and changing chapters

Return to the original scene and inspect a subsequent chapter’s context. Sources may expose chapter or work discussions differently. Reopen to check preference persistence and state the tested scope. Either manual lookup or supported chapter-end placement can be suitable without a uniform social interface across all formats.

Acceptance and limits

Finish with known source support, correct discussion identity, understood empty/error results and reliable return navigation. Local files do not inherit a source community, and hiding placement does not delete remote discussion. This read-only inspection does not require posting or broader data resets.

Maintain ManYue sources: updates, search scope and access failures; ManYue continuous chapter transitions: verify endings, next chapters and stopping.

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.