feat(render): the Cesium renderer passes every conformance check a page can run

- Cesium's own tweens (its flights) step on the renderer's clock, so the
  flight traces compare frame by frame; dispose gives the scene its own
  clock back.
- moveStart and moveEnd are measured each tick on that clock, by the
  shared move detection, a change of the field of view or aspect
  included; Cesium's own events timed them by the system clock.
- A follow of a drawn item tracks where the draw port draws it.
- Pick rays are summed from the eye's axes: Cesium's lose about 1e-9 of
  direction at a near plane of 0.1 m. Ellipsoid picks and the view
  rectangle use them; a canvas with no size has none, as in Cesium.
- The harness always runs the virtual clock and claims 120 checks: 119
  pass on the page and query.heights skips. The five pointer traces
  need a camera controller there, and are recorded from Cesium's own
  controller in Node.
- The package boundaries list the cesium plugin export and the modules
  its groups now import.
This commit is contained in:
Sameh Khamis committed 2026-11-12 14:59:45 -08:00
1 parent 720932e1f9
commit e9085e8df3
13 files changed
+545 -95

No files matched your search

+6 -2
View File
@@ -453,8 +453,12 @@ test('a sky-facing camera yields no frame and both actions decline', () => {
scene.pickPosition = () => null;
scene.globe.pick = () => undefined;
scene.requestRender = () => {};
camera.getPickRay = () => new Cesium.Ray();
camera.pickEllipsoid = () => undefined;
// 1000 km up, looking above the horizon: no ray from the centre meets
// the ellipsoid.
camera.setView({
destination: Cesium.Cartesian3.fromDegrees(-97.74, 30.27, 1_000_000),
orientation: { heading: 0, pitch: Cesium.Math.toRadians(30), roll: 0 },
});
const viewer = withPorts({ camera, scene });
assert.equal(readCameraTargetFrame(viewer), null);