Seekbar Locked After Course Completion Relaunch

You're not imagining it — this matches the widely reported behavior, and your testing rules out the usual suspects (revisit settings, browser, SCORM version). "Allow drag after completion" is a runtime event, not a persisted setting: the unlock fires when completion triggers during a session, and nothing about that unlocked state gets written anywhere that survives a relaunch. Resume restores your suspend data — variables, slide position — but the player's seekbar lock gets initialized from scratch, so you're locked again.

To your questions: 1) Expected, yes — I haven't seen official documentation calling it a limitation, but it's consistently reproducible, including in exactly your setup. 2) No Storyline-only method — there is no trigger action that locks or unlocks the seekbar, so triggers simply can't touch it. 3) JavaScript is still the only workaround I've seen, and it's DOM-level (toggling the seekbar element's interactivity, usually gated on a persisted "completed" variable). That means unsupported and potentially fragile across player updates — if you go that route, retest on every Storyline release.

One design-side alternative, since the course is a single slide: do you actually need the seekbar? Hiding it and using your own navigation removes the whole problem — no locked state to fight, and completion still reports normally. What's the real learner need for scrubbing on relaunch — reviewing content, or something else? That changes which workaround is worth the effort.