Launchers¶
A launcher is a persistent control placed next to an element. Pressing it runs an action, typically starting a walkthrough or opening a documentation link.
Settings¶
| Setting | Values |
|---|---|
| Style | icon, button, link |
| Icon | help, info, play, document, new |
| Placement | Relative to the anchor element |
| Label and tooltip | Text shown on the control and on hover |
| Action | start-content, open-resource, open-url, open-resource-center, dismiss, acknowledge |
A walkthrough with the trigger type launcher starts when a launcher runs start-content for it.
Worked example¶
Put a "How do I?" link beside a form title:
- New content, Launcher. Name it "Intake help".
- Pick the page heading as the anchor.
- Style
link, label "How do I enter a claim?". - Action
start-content, target the intake walkthrough. Publish. - On the walkthrough, set the trigger to launcher so it only runs from this control.
Gotchas¶
- Announcements cannot use a launcher trigger. The Checks panel warns with
trigger-unsupported. - Launchers inside iframes work for same-origin frames and, through the frame agent, for one cross-origin hop. See known limits.
- Icons and the help bubble can collide in a corner. The help bubble can be moved in app settings.