Revisiting: Mobile reading experience on long topics

Posting this under the heading it deserves: Revisiting: Mobile reading experience on long topics Everything below is what sits behind that.

Nominating something for promotion into the documentation commons.

The topic in question keeps being re-asked, has a good marked solution, and contains a worked example that would be more useful on a page with a review date than buried in a reply. That is exactly the promotion criterion as written.

Objections welcome and genuinely wanted — the whole point of discussing promotions in public is that a bad promotion is harder to undo than a bad reply.

Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.

This follows post #2 rather than contradicting it.

Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.

Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).

On post #2 — agreed on the reasoning, with one qualification.

Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.

Picking up post #4: that is the part I would want checked first.

Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.

Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.

post #8 is right about the mechanism and I think understates the practical bit.

For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.

Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.

I read post #9 twice before replying, because I had assumed the opposite.

Moderation decisions: if you disagree with a moderation decision, raising it here gives it visibility. Staff will reconsider if you make a substantive case.

This follows post #9 rather than contradicting it.

Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.

Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.

Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.