In dreamstream-cluster-dashboard.component.tsinitThreeJS, stats.js is only created when innerWidth >= 1024 || innerWidth <= 768. The comment above the gate says desktop and mobile both get the FPS panel, but an iPad-sized viewport (e.g. 800×600) falls in the hole and never mounts #fpsHost / the floating fallback.
Would catch: widening the gate to >= 800 (or always constructing stats) makes the tablet-skip unit test RED — the panel appears where production currently leaves stats undefined.
Suggested fix: treat anything <= 1024 as the scaled mobile/tablet path, or drop the exclusive-or and always attach stats (toolbar slot already scales to 0.6).
In `dreamstream-cluster-dashboard.component.ts` `initThreeJS`, stats.js is only created when `innerWidth >= 1024 || innerWidth <= 768`. The comment above the gate says desktop **and** mobile both get the FPS panel, but an iPad-sized viewport (e.g. 800×600) falls in the hole and never mounts `#fpsHost` / the floating fallback.
Would catch: widening the gate to `>= 800` (or always constructing stats) makes the tablet-skip unit test RED — the panel appears where production currently leaves `stats` undefined.
Suggested fix: treat anything `<= 1024` as the scaled mobile/tablet path, or drop the exclusive-or and always attach stats (toolbar slot already scales to 0.6).
Resolved in spikersoft-angular PR #819 (merged to master). Our Stack dashboard keeps the FPS monitor on tablet widths (769–1023px). Closing.
Resolved in spikersoft-angular [PR #819](https://git.spikersoft.com/spikerj/spikersoft-angular/pulls/819) (merged to `master`). Our Stack dashboard keeps the FPS monitor on tablet widths (769–1023px). Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In
dreamstream-cluster-dashboard.component.tsinitThreeJS, stats.js is only created wheninnerWidth >= 1024 || innerWidth <= 768. The comment above the gate says desktop and mobile both get the FPS panel, but an iPad-sized viewport (e.g. 800×600) falls in the hole and never mounts#fpsHost/ the floating fallback.Would catch: widening the gate to
>= 800(or always constructing stats) makes the tablet-skip unit test RED — the panel appears where production currently leavesstatsundefined.Suggested fix: treat anything
<= 1024as the scaled mobile/tablet path, or drop the exclusive-or and always attach stats (toolbar slot already scales to 0.6).Resolved in spikersoft-angular PR #819 (merged to
master). Our Stack dashboard keeps the FPS monitor on tablet widths (769–1023px). Closing.