# [Bug] Globe Interaction Disabled After Returning from Country Details #1114

New Issue

2026-08-27T22:45:19Z

enjin2310 commented

2026-08-27 22:45:19 +00:00

Summary

After viewing a country’s details in the Geography Explorer, returning to the globe view disables interactive features such as country selection and hover highlights. The pointer remains visible, but the selection and hover functionality no longer respond.

Issue Description

When a user explores a country and then navigates back to the globe view, the globe becomes non-interactive. Although the pointer cursor persists, clicking on highlighted countries does not trigger exploration, and hover visual feedback (highlighting) is missing. The issue suggests that the interactive layer or event listeners are not reinitialized after returning from the country details view.

Environment

Property	Value
Application	SpikerSoft Learn
Module	Geography Explorer
Environment	Production
Browser	Firefox
Operating System	Windows 11
Version	v2026.08.27e
Device	Desktop

Preconditions

User must have previously opened a country’s details page from the globe view.

Steps to Reproduce

Log in to the SpikerSoft platform.
Navigate to Learn > Geography Explorer.
Click on a highlighted country to view its details.
Return to the globe view using the back navigation or “Explore” button.
Attempt to hover or click on other countries.

Expected Result

The globe should remain fully interactive, allowing users to hover and select new countries for exploration.

Actual Result

The globe becomes static:

Hover highlighting is disabled.
Clicking on countries has no effect.
The pointer cursor remains visible but non-functional.

Evidence

The screenshot shows the Geography Explorer globe with the pointer active but no visible hover highlights.
The bottom instruction text (“Arrastra para girar el globo — haz clic en un país resaltado para explorarlo”) remains displayed, but interaction is unavailable.

Impact

Prevents users from continuing exploration without refreshing the page.
Breaks the intended interactive flow of the Geography module.
Reduces usability and engagement.

Frequency

Always

Reproducibility

100%

Severity

High

## Summary After viewing a country’s details in the **Geography Explorer**, returning to the globe view disables interactive features such as country selection and hover highlights. The pointer remains visible, but the selection and hover functionality no longer respond. ## Issue Description When a user explores a country and then navigates back to the globe view, the globe becomes non-interactive. Although the pointer cursor persists, clicking on highlighted countries does not trigger exploration, and hover visual feedback (highlighting) is missing. The issue suggests that the interactive layer or event listeners are not reinitialized after returning from the country details view. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Learn | | Module | Geography Explorer | | Environment | Production | | Browser | Firefox | | Operating System | Windows 11 | | Version | v2026.08.27e | | Device | Desktop | ## Preconditions User must have previously opened a country’s details page from the globe view. ## Steps to Reproduce 1. Log in to the SpikerSoft platform. 2. Navigate to **Learn > Geography Explorer**. 3. Click on a highlighted country to view its details. 4. Return to the globe view using the back navigation or “Explore” button. 5. Attempt to hover or click on other countries. ## Expected Result The globe should remain fully interactive, allowing users to hover and select new countries for exploration. ## Actual Result The globe becomes static: - Hover highlighting is disabled. - Clicking on countries has no effect. - The pointer cursor remains visible but non-functional. ## Evidence - The screenshot shows the **Geography Explorer** globe with the pointer active but no visible hover highlights. - The bottom instruction text (“Arrastra para girar el globo — haz clic en un país resaltado para explorarlo”) remains displayed, but interaction is unavailable. ## Impact - Prevents users from continuing exploration without refreshing the page. - Breaks the intended interactive flow of the Geography module. - Reduces usability and engagement. ## Frequency Always ## Reproducibility 100% ## Severity High

Screenshot 2026-08-27 184304.png

575 KiB

spikerj referenced this issue from a commit

2026-08-30 19:33:55 +00:00

fix: don't build a globe after destroy; replay dropped highlights (fixes #893)

spikerj commented

2026-08-30 19:34:35 +00:00

Found it — and your screenshot is what cracked it, so thank you for attaching one.

It is not a repeat of the earlier globe fix. That one is deployed, and your screenshot rules it out directly: the countries are painted orange and grey, so the globe does have its data. It also rules out a stuck loading overlay (that would dim and blur the whole page — yours is crisp) and a bad asset path (I checked, because a different bug you filed, #1111, was exactly that).

What is actually wrong. The country-details view and the globe are siblings in the same page, so opening a country destroys the globe and coming back builds a new one. That round trip had no test coverage at all, and two things were wrong in it:

The globe loads a ~250 KB map file on every single mount, and clicking a country tears the component down while that download is still running. The teardown code was written to only run if the globe already existed — which, mid-download, it does not. So teardown quietly did nothing, and the download then finished and built a globe into a page that was already gone: a second renderer, an animation loop nobody could ever stop, and a size-watcher attached to a detached element. Browsers only allow about 16 WebGL contexts; leaking one per country you visit ends exactly where you landed — a globe that draws but does not respond.
Separately, highlight data arriving before the globe finished loading was silently dropped with nothing to replay it.

Fix: spikerj/spikersoft-angular#894. The teardown now always runs and marks the component dead, and the load path checks that flag before building anything.

A note on your repro steps: you wrote "click a country → return". The leak needs the click to land while the map file is still downloading, so on a fast connection it may take a few round trips to go dead rather than one. If you can tell me roughly how many countries you visited before it stopped responding, that is genuinely useful — it tells us how close to the context limit the page runs.

Will close once it merges and deploys.

Found it — and your screenshot is what cracked it, so thank you for attaching one. **It is not a repeat of the earlier globe fix.** That one is deployed, and your screenshot rules it out directly: the countries are painted orange and grey, so the globe *does* have its data. It also rules out a stuck loading overlay (that would dim and blur the whole page — yours is crisp) and a bad asset path (I checked, because a different bug you filed, #1111, was exactly that). **What is actually wrong.** The country-details view and the globe are siblings in the same page, so opening a country **destroys** the globe and coming back **builds a new one**. That round trip had no test coverage at all, and two things were wrong in it: 1. The globe loads a ~250 KB map file on every single mount, and clicking a country tears the component down *while that download is still running*. The teardown code was written to only run if the globe already existed — which, mid-download, it does not. So teardown quietly did nothing, and the download then finished and built a globe into a page that was already gone: a second renderer, an animation loop nobody could ever stop, and a size-watcher attached to a detached element. Browsers only allow about 16 WebGL contexts; leaking one per country you visit ends exactly where you landed — a globe that draws but does not respond. 2. Separately, highlight data arriving before the globe finished loading was silently dropped with nothing to replay it. **Fix:** spikerj/spikersoft-angular#894. The teardown now always runs and marks the component dead, and the load path checks that flag before building anything. A note on your repro steps: you wrote "click a country → return". The leak needs the click to land *while the map file is still downloading*, so on a fast connection it may take a few round trips to go dead rather than one. If you can tell me roughly how many countries you visited before it stopped responding, that is genuinely useful — it tells us how close to the context limit the page runs. Will close once it merges and deploys.

spikerj commented

2026-08-30 23:54:23 +00:00

Fixed and merged — closing.

The globe kept building after the component was destroyed, leaking its WebGL context so the next visit had none left. Guarded, with dropped highlights replayed (spikerj/spikersoft-angular#894).

The change is on master and deployed. Please re-test when you get a chance; if you still see it, reopen this issue rather than filing a new one so the history stays together.

Fixed and merged — closing. The globe kept building after the component was destroyed, leaking its WebGL context so the next visit had none left. Guarded, with dropped highlights replayed (spikerj/spikersoft-angular#894). The change is on `master` and deployed. Please re-test when you get a chance; if you still see it, reopen this issue rather than filing a new one so the history stays together.

spikerj closed this issue

2026-08-30 23:54:23 +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#1114