Fly the camera through the renderer's camera port

The Cesium camera port moves into render/cesium/camera.js, with the
listener list and position conversion shared from common.js. It now
covers flights (flyTo, flyToBounds, cancelFlight, flying), lookAt and
release, command hooks, and a flightEnd event for the flights it starts.

A flight's end that Cesium raises inside one of the port's own calls is
delivered once Cesium's call returns, so its callback sees the flight
let go of. A flight Cesium declines to start, mid scene-mode morph,
ends as cancelled instead of never settling.

Flight traces run in Node on the recorder's headless camera with a
virtual clock; the browser harness keeps the instant traces.

The startup fly-in, landmark and viewport flights, share-link restore
and the shell's camera state now go through the port. camera.js and
sharelink.js leave the Cesium allow-list.
This commit is contained in:
Sameh Khamis committed 2026-11-05 20:15:52 -08:00
1 parent b5900b4178
commit 46a53bb49c
20 files changed
+846 -305

No files matched your search

+2 -1
View File
@@ -456,12 +456,13 @@ test('share-link restore forces a final stationary render for Google 3D Tiles',
assert.ok(calls.flyTo, 'restore must start a camera flight');
assert.equal(typeof calls.flyTo.complete, 'function');
const rendersInFlight = calls.renders;
calls.flyTo.complete();
assert.deepEqual(calls.setView, {
destination: calls.flyTo.destination,
orientation: calls.flyTo.orientation,
});
assert.equal(calls.renders, 1);
assert.equal(calls.renders, rendersInFlight + 1, 'one render at rest');
});
test('newer navigation suppresses delayed share camera while non-camera state still restores', async () => {