pastilhas
585f234b5b
`initialPath` and `defaultSort` reached `FileBrowserApp` from nowhere else — the panel wrapper was their only caller, and it was passing the two context fields that had no setter. Both remaining callers pass neither, so the whole chain below them was already running on its defaults. That includes `isolated`, which was `!!initialPath` and therefore always false: the unscoped browser has been mirroring its folder into `files/currentPath` unconditionally, which is what the comment beside it describes. Same behaviour, one fewer flag that reads as if it sometimes fires.