@displayxr/inline3d 1.47.4 → 1.47.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/dist/call.js +5 -5
- package/js/camera/capture.js +31 -13
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,19 @@ which tier they touch, because that is what tells you whether an upgrade can mov
|
|
|
7
7
|
|
|
8
8
|
## Unreleased
|
|
9
9
|
|
|
10
|
+
## 1.47.5 — 2026-11-01
|
|
11
|
+
|
|
12
|
+
### Fixed — the camera permission prime could open a phone lens and crash its camera (`./camera`, `./call`)
|
|
13
|
+
|
|
14
|
+
Before camera permission, `openCamera('auto')` primed on `{1280x720, facingMode: 'environment'}`.
|
|
15
|
+
On a phone whose lenses all report the same facing, that picked camera 0, one lens of the 3D
|
|
16
|
+
camera's pair, and on some phones a plain open of that lens, or its teardown, crashes the camera
|
|
17
|
+
service. The prime now asks for the default camera with no constraints. The DisplayXR Browser lists
|
|
18
|
+
its 3D camera first, so the prime opens the pair directly and no lens is opened. A desktop webcam is
|
|
19
|
+
still opened once and kept, and is then asked for the usual 1280x720 mode without a second start.
|
|
20
|
+
With labels visible but no 3D camera listed, the list is read once more before the fallback, since
|
|
21
|
+
a runtime 3D camera can appear late after a runtime restart.
|
|
22
|
+
|
|
10
23
|
## 1.47.4 — 2026-10-31
|
|
11
24
|
|
|
12
25
|
### Fixed — a declared 3D camera with portrait eyes was dropped for a plain one (`./camera`, `./call`)
|