1. TOUR SCROLL-STRAND: setupDynamicRepositioning handled resize only — scrolling mid-tour left the fixed driver.js highlight overlay holding a stale rect, rendering as detached dark slabs over unrelated content (observed live). Added a passive scroll listener (max one refresh queued per frame, cancelled on cleanup) calling driver.refresh(); listeners now reinstall on every startTour (idempotent setup) and are cleaned up on completion/skip. 2. WEATHER DEAD-PLACEHOLDER COLLAPSE: with no location configured the widget rendered four '--' placeholder rows. Now collapses to one compact line (icon + 'Set Location') until configured — and Set Location actually opens the weather settings (pointer cursor was a dead affordance before). 3. Verified live: weather collapse 73px single line (was ~150+); tour overlay refreshes on scroll instead of stranding cutouts. Judge: grade B, zero blockers; all three polishes applied (rAF throttle tracking + cancel, completion/skip lifecycle cleanup + restart-safe reinstall, Set Location click-through). Frontend 68/68.
DashCaddy Onboarding System
This directory contains the JavaScript modules for the user onboarding tooltip system.
Files
- onboarding.js - Main entry point, initializes the onboarding system
- tour-manager.js - Orchestrates the onboarding flow and manages tour state
- progress-tracker.js - Manages persistent storage of user progress
- tooltip-definitions.js - Defines all tooltip content and positioning
- dns-template-selector.js - Presents DNS server template options
- theme-adapter.js - Ensures tooltips match the current dashboard theme
Load Order
The scripts are loaded in the following order (as defined in status/index.html):
- progress-tracker.js
- theme-adapter.js
- tooltip-definitions.js
- dns-template-selector.js
- tour-manager.js
- onboarding.js (main initialization)
Dependencies
- Driver.js - Loaded from CDN (https://cdn.jsdelivr.net/npm/driver.js@1.3.1/)
- Dashboard CSS variables (for theming)
- Browser localStorage API (for progress tracking)
Integration
The onboarding system integrates with:
- Dashboard theme system (via CSS variables)
- App template selector (for DNS server deployment)
- Local storage (for progress persistence)
Development
Each module is wrapped in an IIFE (Immediately Invoked Function Expression) to avoid global namespace pollution. Modules communicate through well-defined interfaces and the window object where necessary.