ENGLISH·COURSE API
    Preparing search index...
    • The indicator drawn over the tapped half of the video while a seek run is active: a translucent half-disc, three chevrons pointing the way the video moved, and the seconds the run has seeked so far.

      Parameters

      • direction: { direction: SeekDirection; seconds: number }

        The way the run moved the video; picks the side and the glyph

      Returns Element

      It is an ordinary child of the player box, absolutely positioned against it, so it moves with the pinned player and needs no portal. Whether it is on screen is not its decision: the player's gesture helper renders it while a run is active and unmounts it when the run lapses.

      It never takes the pointer. The taps that keep a run alive land on the provider underneath, and an indicator that swallowed them would end the very run it shows.

      The direction lives in the glyph, not in a class. ChevronLeft for a backward run and ChevronRight for a forward one — never one glyph flipped by a transform. ScrollDownHint records why: a phone that picks up new JS while holding a cached stylesheet must still draw chevrons that point the way the video moved. What CSS carries here is the pulse, and a stylesheet that never arrives costs the motion, never the direction.

      role="status" lets assistive technology hear the seek without focus leaving the player. A chevron states nothing there, so forward / backward carry the direction in words and the visible count is aria-hidden — both sit in the same region, and without that the seconds are read twice. The pulse is dropped under prefers-reduced-motion, which leaves the still chevrons and the count.