files-app becomes url-state: the file browser is where the work happened, but where selection lives and who clears a query string are framework questions. The panel framework's version of the same question moves in beside them, extracted from the deep-read item, which keeps it as one of its three questions. Item ids changed with the theme. Done now deliberately — no board reads them yet, and this is the last cheap moment to move one. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
16 lines
707 B
Markdown
16 lines
707 B
Markdown
---
|
|
id: url-state/the-acts-that-clear-the-overlay-have-no-owner
|
|
title: "The acts that clear the overlay have no owner, only the list does"
|
|
theme: url-state
|
|
status: open
|
|
created: 2026-08-20
|
|
date_source: assumed
|
|
order: 2
|
|
---
|
|
|
|
**The acts that clear the overlay have no owner, only the list does.** `VIEWER_PARAMS` and
|
|
`withoutViewerParams` live in `files-route.ts` and are shared. But every site still decides FOR
|
|
ITSELF whether to call them, which is precisely how the breadcrumb shipped wrong an hour after the
|
|
rule was written. Three bugs in a row came from this. A single `navigateToFolder()` that every
|
|
caller must go through — rather than a helper they may remember — is the fix if a fourth appears.
|