Persist CI Cargo caches and repair runtime regression coverage
Verify Tessera GUI / verify (push) Successful in 1m40s
Verify Tessera GUI / verify (push) Successful in 1m40s
This commit is contained in:
@@ -228,3 +228,10 @@ A waiting coroutine retains its evaluated operand and frames as managed edges; w
|
||||
|
||||
|
||||
While a native tab drag is held over an overflow arrow area, the strip waits 350ms then reveals one hidden tab every 120ms, including in a compatible destination window. The preview scroll does not activate Pages or change business state. Drawing, hit testing and insertion gaps share the same transient visible range; release uses its full-order insertion index. Leaving the strip stops the timer; release, Escape, a new press or runtime generation change restores the normal active-tab-centered strip. A resize or changing tab count clamps the range. Native drag/mixed-DPI behavior still requires platform validation; application-exit lifecycle notifications remain unfinished.
|
||||
|
||||
CI regression fixtures use the published frame's session identity for input,
|
||||
current Endor statement boundaries/type names and the retained runtime's actual
|
||||
layout/paint pipeline. Failed first Console rendering discards unpublished Page
|
||||
registrations through host-only cleanup, preventing the next successful query
|
||||
from silently opening a previously failed pending render. Earlier ordinary
|
||||
bindings remain live; explicit page.render can subsequently publish the Page.
|
||||
|
||||
Reference in New Issue
Block a user