CameraMoveOptions.durationMs ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

Property of CameraMoveOptions · stable · since 2.0.0

ts
durationMs?: number;

0 lands exactly, without damping, before the next frame. A move called after a durationMs: 0 write to the same target (a view after a view, a lens after a lens), in the same task too, starts from that write's value, never from the one last drawn: a 0 ms set then an eased set jumps, then glides. Camera.state says when a read returns that value. Counts as 0 while the shopper's system asks for reduced motion (spec section 6.2).

Default: 0

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: durationMs names no product
2. A precedent pass: Unity Transform.LookAt (row G42); Babylon.js ArcRotateCamera setTarget, setPosition (row G42); Babylon.js ArcRotateCamera lowerAlphaLimit, upperAlphaLimit, panning (row G7)
3. Two apps, or labs pass: 6 apps (ledger: app-4f16d2f6da, app-b362a81c85, app-f9a32142f1, app-fc07850558, app-fc306ec3dc, app-fd09090420)
4. The cheaper fix first decided per need in Appendix B: rows G42, G7 at tier stable (a member only where no rule, data, asset or app code serves the need)