User Story
- As a reader
- I want tapping a passage to take me to the exact place in the article it came from
- So that I can read it in context without hunting for it
Where in the flow: Transition from the Dive sheet into the article view. Section jumping is a property of result presentation across all Phase 2 approaches, not a feature specific to this arm.
Acceptance criteria
- Tapping a card or show more opens the source article scrolled to the passage’s section anchor.
- The passage is highlighted in the article on arrival, spanning several consecutive lines, using the same token as the passage card in US-5.
- The highlight does not persist across navigation or app restart.
- The highlight sits behind the text without obscuring inline reference markers or links.
- When the passage has no section anchor, the reader lands at the top of the article without an error.
- Back from the article returns the reader to the search screen with the query, the entry point, and the autocomplete list intact — not to a blank search.
[] The query is written to search history so the reader can return to it (see US-10).
TS: Per sync with Jaz on Sept 16, it was decided that the query is written to the "recent searches" list when navigating to Article (current behavior for all users).
- The tap is logged with enough detail to reconstruct the funnel: query, result position, article, section.
TS: There should be handling if we fail to seek out the article text and scroll / highlight it (i.e. if an article has since been edited to remove text). We should show an error message in that case (TBD by design).
Notes and open questions
- Highlighting depends on the Search team’s highlighting work — a cross-team dependency, not work in this task.
- Test behaviour when the anchor no longer exists in the live article because a section was renamed or removed.
- On Android the article bottom toolbar already contains "Find in article" and may need to be suppressed for experiment to cut confusion.
Design
Note: Both platforms - please update the "link" (iOS) and "progressive color" (Android) in black and dark mode to follow what we have in Codex. Noted in Figma. Android, please follow the same token as iOS.
Android: please update the highlight tokens to match iOS (find-in-page). We'll use the findInPageMatch token for semantic search highlights, and they vary by theme (dark/light) — see the reference image. Also, when text has a highlight behind it, blue links within that passage should switch to underlined — see Figma for an example. Let me know if you have any questions.

