[critical]: Loading animation triggers on every keystroke (accessibility hazard) #106

New Issue

2026-05-11T14:46:21Z

enjin2310 commented

2026-05-11 14:46:21 +00:00

Each time a letter is typed on the page, the loading animation of learn.spikersoft.com appears and renders.

Observed behavior:

Typing any character triggers the loading animation to display.
The animation appears repeatedly for each keystroke.
This creates a distracting and potentially harmful visual effect.

Health & accessibility impact:

The repeated flashing animation could trigger headaches.
The rapid, repetitive visual stimuli poses a potential risk for users with photosensitivity or epilepsy.
The behavior is disruptive to normal typing and user experience.

Expected behavior:

The loading animation should only display when the page is actually loading content.
Typing should not trigger any loading animation.
The page should remain stable and responsive without visual artifacts during input.

Classification:

Type: bug
Area: UI / loading state
Severity: high (accessibility and health concern)
Priority: critical

Each time a letter is typed on the page, the loading animation of learn.spikersoft.com appears and renders. Observed behavior: - Typing any character triggers the loading animation to display. - The animation appears repeatedly for each keystroke. - This creates a distracting and potentially harmful visual effect. Health & accessibility impact: - The repeated flashing animation could trigger headaches. - The rapid, repetitive visual stimuli poses a potential risk for users with photosensitivity or epilepsy. - The behavior is disruptive to normal typing and user experience. Expected behavior: - The loading animation should only display when the page is actually loading content. - Typing should not trigger any loading animation. - The page should remain stable and responsive without visual artifacts during input. Classification: - Type: bug - Area: UI / loading state - Severity: high (accessibility and health concern) - Priority: critical

Screen Recording 2026-04-25 234329.mp4

2.7 MiB

enjin2310 changed title from ~~bug: Loading animation triggers on every keystroke (accessibility hazard)~~ to [critical]: Loading animation triggers on every keystroke (accessibility hazard)

2026-05-11 14:47:43 +00:00

spikerj commented

2026-06-07 18:16:21 +00:00

Root cause: the global LoadingInterceptor shows the spinner overlay for every HTTP request, and LoadingDisplayService attached it on the next microtask. Inputs across the app fire short-lived requests per keystroke, so each near-instant request flashed the spinner — the repetitive flashing you flagged.

Fix in spikerj/spikersoft-angular#1: the overlay now only appears after a 300ms grace period, so fast per-keystroke requests never paint it while genuinely slow loads still do. Cancelled on completion so a quick request leaves no flash. fakeAsync regression tests added.

Closing as fixed by spikerj/spikersoft-angular#1.

Root cause: the global `LoadingInterceptor` shows the spinner overlay for every HTTP request, and `LoadingDisplayService` attached it on the next microtask. Inputs across the app fire short-lived requests per keystroke, so each near-instant request flashed the spinner — the repetitive flashing you flagged. Fix in spikerj/spikersoft-angular#1: the overlay now only appears after a 300ms grace period, so fast per-keystroke requests never paint it while genuinely slow loads still do. Cancelled on completion so a quick request leaves no flash. fakeAsync regression tests added. Closing as fixed by spikerj/spikersoft-angular#1.

spikerj closed this issue

2026-06-07 18:16:29 +00:00

spikerj referenced this issue

2026-07-03 19:39:32 +00:00

[Bug] Blockly tool crashes on load — ViewChild resolves undefined under *transloco (same class as diagram #314 finding) #342

spikerj referenced this issue

2026-07-03 19:39:34 +00:00

[Bug] /tree-of-knowledge calls GET /api/activity/progress anonymously → 401 console error (class of #312) #343

spikerj referenced this issue

2026-07-03 19:39:44 +00:00

[E2E P0] Harness & telemetry foundation #313

spikerj referenced this issue