# [Bug] Globe Interaction Unresponsive — Pointer Active but No Highlight or Click #1132

New Issue

2026-09-01T23:17:31Z

enjin2310 commented

2026-09-01 23:17:31 +00:00

Summary

In the Geography Explorer module of SpikerSoft, the interactive globe intermittently fails to respond to user input. The pointer remains visible and movable, but hover highlights and click actions on countries are inconsistent — sometimes functioning correctly, other times completely unresponsive.

Issue Description

Users can move the pointer over the globe, but hover and click events behave unpredictably. At times, countries highlight and respond to clicks as expected; at other times, the same interactions produce no visual or functional feedback. This inconsistency suggests unstable event binding or race conditions in the interaction layer.

Environment

Property	Value
Application	SpikerSoft Learn
Module	Geography Explorer
Environment	Production
Browser	Edge
Operating System	Windows 11
Version	v2026.09.01a
Device	Desktop

Steps to Reproduce

Log in to the SpikerSoft platform.
Navigate to Learn > Geography Explorer.
Attempt to hover or click on any highlighted country.
Observe that sometimes the highlight and click events work, and other times they do not.

Expected Result

Hovering over a country should consistently trigger a highlight effect, and clicking should always open the country’s details page.

Actual Result

Pointer remains active.
Hover and click events are inconsistent.
Globe rotation and exploration occasionally fail.
No clear pattern to when interaction succeeds or fails.

Evidence

Screenshot shows the globe centered on North America with pointer active but no visible hover highlights.

Impact

Unreliable user experience.
Breaks core interactive functionality.
Reduces engagement and usability.

Frequency

Intermittent

Reproducibility

~60–70%

Severity

Major

Notes

The issue appears to be caused by unstable event listener registration or conditional rendering conflicts. It may involve asynchronous initialization of the globe component or delayed DOM updates preventing consistent event capture.

## Summary In the **Geography Explorer** module of **SpikerSoft**, the interactive globe intermittently fails to respond to user input. The pointer remains visible and movable, but hover highlights and click actions on countries are inconsistent — sometimes functioning correctly, other times completely unresponsive. ## Issue Description Users can move the pointer over the globe, but hover and click events behave unpredictably. At times, countries highlight and respond to clicks as expected; at other times, the same interactions produce no visual or functional feedback. This inconsistency suggests unstable event binding or race conditions in the interaction layer. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Learn | | Module | Geography Explorer | | Environment | Production | | Browser | Edge | | Operating System | Windows 11 | | Version | v2026.09.01a | | Device | Desktop | ## Steps to Reproduce 1. Log in to the SpikerSoft platform. 2. Navigate to **Learn > Geography Explorer**. 3. Attempt to hover or click on any highlighted country. 4. Observe that sometimes the highlight and click events work, and other times they do not. ## Expected Result Hovering over a country should consistently trigger a highlight effect, and clicking should always open the country’s details page. ## Actual Result - Pointer remains active. - Hover and click events are inconsistent. - Globe rotation and exploration occasionally fail. - No clear pattern to when interaction succeeds or fails. ## Evidence Screenshot shows the globe centered on North America with pointer active but no visible hover highlights. ## Impact - Unreliable user experience. - Breaks core interactive functionality. - Reduces engagement and usability. ## Frequency Intermittent ## Reproducibility ~60–70% ## Severity Major ## Notes The issue appears to be caused by unstable event listener registration or conditional rendering conflicts. It may involve asynchronous initialization of the globe component or delayed DOM updates preventing consistent event capture.

Screenshot 2026-09-01 191337.png

399 KiB

spikerj commented

2026-09-04 14:47:22 +00:00

Diagnosed and fixed in spikerj/spikersoft-angular#935.

Reproduced against the production bundle with live data: on a cold load the globe raycasts fine (cursor changes) but shows 0 hover labels across 108 samples and clicks do nothing; after switching layout away and back, 14 labels and clicks navigate. Cause: on first load the globe paints before the countries request resolves and then re-applies the real highlights — and three-globe treats those as in-place updates (it keys on an __id it had stamped onto our shared GeoJSON), so the countries recolor but keep stale hover/click data. The fix hands three-globe fresh datums every paint. Regression tests fail pre-fix; the rebuilt bundle shows labels and a working click on first load.

Diagnosed and fixed in spikerj/spikersoft-angular#935. Reproduced against the production bundle with live data: on a cold load the globe raycasts fine (cursor changes) but shows **0 hover labels across 108 samples** and clicks do nothing; after switching layout away and back, 14 labels and clicks navigate. Cause: on first load the globe paints before the countries request resolves and then re-applies the real highlights — and three-globe treats those as in-place updates (it keys on an `__id` it had stamped onto our shared GeoJSON), so the countries recolor but keep stale hover/click data. The fix hands three-globe fresh datums every paint. Regression tests fail pre-fix; the rebuilt bundle shows labels and a working click on first load.

spikerj commented

2026-09-06 03:38:25 +00:00

Closing — fix merged in spikerj/spikersoft-angular#935 (2026-09-04) and is on master: the globe never receives a datum still carrying a previous paint's __id, so the cold-load paint binds hover/click correctly.

Closing — fix merged in spikerj/spikersoft-angular#935 (2026-09-04) and is on master: the globe never receives a datum still carrying a previous paint's `__id`, so the cold-load paint binds hover/click correctly.

spikerj closed this issue

2026-09-06 03:38:26 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#1132