@condorinst/mobile-bridge 0.15.0 → 0.15.2
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 +42 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.15.2] — 2026-08-31
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **`client_demo` (examples-only): the other device's BLE event wiped the
|
|
15
|
+
history charts.** Second cause of the same symptom as `0.15.1`, found on
|
|
16
|
+
device after that fix: the charts vanished on their own, seconds after being
|
|
17
|
+
drawn, with nobody touching the screen.
|
|
18
|
+
|
|
19
|
+
`handleDeviceConnection` guarded its rerender with
|
|
20
|
+
`chartsAreLive() && selectedSerialNo === payload.serialNo`, which let through
|
|
21
|
+
exactly the event of the **other** device — the 7047 was on screen and the
|
|
22
|
+
4800 connecting over BLE re-rendered the page and destroyed the five
|
|
23
|
+
canvases. The guard meant to protect the visible device ended up protecting
|
|
24
|
+
only the case that could not hurt it.
|
|
25
|
+
|
|
26
|
+
With charts alive there is now no full rerender: the visible device patches
|
|
27
|
+
its badge, any other device only updates state — its card lives on the home,
|
|
28
|
+
which is rendered when the user goes back.
|
|
29
|
+
|
|
30
|
+
`handleRealTime` has the same shape but genuinely needs its rerender (the
|
|
31
|
+
real-time divs enter and leave the DOM), so it now remounts the history
|
|
32
|
+
charts afterwards instead of leaving the loaded week erased.
|
|
33
|
+
|
|
34
|
+
## [0.15.1] — 2026-08-31
|
|
35
|
+
|
|
36
|
+
### Fixed
|
|
37
|
+
|
|
38
|
+
- **`client_demo` (examples-only): the history charts went blank the moment the
|
|
39
|
+
week finished loading.** `onDone` called the full `rerender()`, which replaces
|
|
40
|
+
the page's `innerHTML` and destroys the live canvases, and then relied on a
|
|
41
|
+
single `requestAnimationFrame` to mount them again. The WebView does not
|
|
42
|
+
always run that frame — a fling suspends them — and when it was skipped
|
|
43
|
+
nothing ever redrew: the section stayed empty, legends gone, until the user
|
|
44
|
+
navigated away. Reproduced on device, on the week that takes ~24 s to load.
|
|
45
|
+
|
|
46
|
+
The end of a load changes exactly one thing on screen: the progress bar goes
|
|
47
|
+
away. That is now a surgical DOM update, so the canvases are never torn down
|
|
48
|
+
and there is no remount to miss. `rerender()` is kept only for the empty week,
|
|
49
|
+
where the structure really does change. `onPage` also self-heals: if the
|
|
50
|
+
charts are not mounted by the time a page lands, it mounts them.
|
|
51
|
+
|
|
10
52
|
## [0.15.0] — 2026-08-31
|
|
11
53
|
|
|
12
54
|
### Added
|
package/package.json
CHANGED