AI media harness for planning, generating, and editing locally
TypeScript
Correct disabled-tooltip rationale, pin range type
Bitti84475bc58b61
diff --git a/src-tauri/src/lib.rs b/src-tauri/src/lib.rsindex 2954e54..66501b4 100644--- a/src-tauri/src/lib.rs+++ b/src-tauri/src/lib.rs@@ -315,7 +315,10 @@ fn validate_and_normalize_config(mut config: ProjectConfig) -> Result<ProjectConconfig.brief.status));}- if !(5..=600).contains(&config.brief.target_duration_seconds) {+ // The bounds are spelled u32 so the range's element type cannot fall back+ // to i32 — `u32: PartialOrd<i32>` does not exist, and this file cannot be+ // compiled on this machine to catch it.+ if !(5u32..=600u32).contains(&config.brief.target_duration_seconds) {return Err(format!("Target duration must be between 5 and 600 seconds, received {}.",config.brief.target_duration_secondsdiff --git a/src/components/workspace/TimelineView.tsx b/src/components/workspace/TimelineView.tsxindex 66ba15a..4ad9105 100644--- a/src/components/workspace/TimelineView.tsx+++ b/src/components/workspace/TimelineView.tsx@@ -168,9 +168,12 @@ export function TimelineView({ config, onChange, onOpenGenerator }: { config: Pr</div><span>{config.settings.resolution.toUpperCase()} · {config.settings.frameRate} fps</span></div>- {/* Browsers don't reliably fire hover on a disabled control, so the- title attributes above may never render. The reason the transport- is dead has to be readable without hovering anything. */}+ {/* Measured in Chromium (the engine behind the WebView2 runtime this+ ships in): a disabled button DOES receive hover and DOES paint its+ title tooltip, so the titles above are not dead. But a tooltip is+ mouse-only — a disabled button cannot take focus, so keyboard and+ touch users have no way to reach it. The reason the transport is+ dead is stated here so it needs no pointer at all. */}{clipCount === 0 && <p className="transport-note">Nothing can be played yet — add or generate a scene and it will land on the timeline below.</p>}</main>diff --git a/src/styles/timeline.css b/src/styles/timeline.cssindex 9670621..fb7bd74 100644--- a/src/styles/timeline.css+++ b/src/styles/timeline.css@@ -484,8 +484,9 @@}/* Sits under the transport rather than inside it, so the 1fr/auto/1fr row keeps- its layout. Disabled buttons swallow hover, so this is the only explanation- an empty transport reliably shows. */+ its layout. The transport's title tooltips do fire on their disabled buttons+ in Chromium, but only for a mouse — this is the explanation everyone else+ gets. */.transport-note {margin: 0;padding: 0 var(--space-4) var(--space-3);