max / quasi

0.44.0: chrome carries a persistent panel, and all three renderers draw it 46fc763c. An always-present floating panel belongs to the app, not to a region every screen repeats. Chrome now carries panel: Option<Panel>, whose contents are an ordinary Node and whose id is the address an answer aims at, so a route that has changed what the panel says reaches it the way it reaches any other region. Where it sits is the renderer's: the webview emits an element with the panel's id and leaves the placement to the stylesheet, the terminal takes a band off the very bottom under the frame, and egui draws it last. The terminal's focus walk counts a panel's controls after the frame's verbs, which is the order the drawing counts in, and View::prune knows about the panel so a field inside one is not dropped as absent from the screen. Nothing dismisses a panel. goingson's time-tracking widget offers Stop and Discard, both of which act on the timer rather than on the panel, so there is no dismissed state to keep and presence stays the app's answer. An app that declares no panel draws exactly what it drew before, asserted per renderer.