CaptureSpec.size ​

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 CaptureSpec · stable · since 2.0.0

ts
size?: {
  width: number;
  height: number;
};

CSS px. 'render' only, as view. At an aspect other than the element's, the capture keeps the lens's held field of view (by default the 60° horizontal one, and after a fit its vertical capped at 45° at the capture's aspect as CameraLens.horizontalFovDeg says); 1.x kept the live vertical one, so such a capture frames differently from 1.x's.

Default: the element's size

Fields ​

width ​

ts
width: number;

height ​

ts
height: number;

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: size names no product
2. A precedent pass: Unity Camera.Render (to a RenderTexture) (row G20); HTMLCanvasElement.toBlob (row K38); Unity ScreenCapture.CaptureScreenshot (row K38)
3. Two apps, or labs pass: 6 apps (ledger: app-4f16d2f6da, app-bcb7ef21da, app-ceb4eccc72, app-e61a0b42ad, app-f3598fad77, app-f9a32142f1)
4. The cheaper fix first decided per need in Appendix B: rows G20, K38 at tier stable (a member only where no rule, data, asset or app code serves the need)