Whether the panel takes the WHOLE page, hiding the tabs and the extension
grid.
Only while a run is live. Hiding the grid during an update is deliberate —
a row of Update buttons beside a running update invites a second one, and the
honest answer to the second press is a refusal.
Hiding it because a run finished is not the same thing, and that is the bug
this function exists to have a name for: showingRun() was used for both, so
one completed update left the page showing nothing but a log, on every load,
with no way to reach the Update buttons at all.
Whether the panel takes the WHOLE page, hiding the tabs and the extension grid.
Only while a run is live. Hiding the grid during an update is deliberate — a row of Update buttons beside a running update invites a second one, and the honest answer to the second press is a refusal.
Hiding it because a run finished is not the same thing, and that is the bug this function exists to have a name for:
showingRun()was used for both, so one completed update left the page showing nothing but a log, on every load, with no way to reach the Update buttons at all.