Hold the shell's inputs between two engines instead of reaching released controllers

A visual choice made while no globe is attached (a style key, a Display control, a voice command) is queued and applied to the next engine's settings after it restored the address's view, so the person's choice wins; reads answer from the released settings. The globe reset and a location lookup started without a globe do nothing, and the map-source chips and camera buttons are unbound until the next globe binds them.
This commit is contained in:
German Khokhlov committed 2026-11-03 19:54:45 +04:00
1 parent df73c5b21a
commit 40a81c58e6
7 files changed
+193 -5

No files matched your search

+16
View File
@@ -86,3 +86,19 @@ test('navigation authority retires deferred flights when the globe changes', ()
const next = navigation._beginDeferredNavigation('location');
assert.equal(navigation._reassertNavigationHandoff(next), true);
});
test('between engines the globe reset neither stamps navigation nor reads a camera', async () => {
const { LocationNavigation } = await import('./ui/locationNavigation.js');
const location = Object.create(LocationNavigation.prototype);
let stamped = 0;
Object.assign(location, {
services: { interruptCameraMotion() {} },
engine: null,
_disposed: false,
_stampNavigation: () => stamped++,
});
const result = await location.resetToGlobeView();
assert.equal(result.ok, false);
assert.equal(result.cancelled, true);
assert.equal(stamped, 0);
});