Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Basemap not showing (immediately) on login #1627

Open
tenda1-wbm opened this issue Oct 6, 2024 · 0 comments
Open

[BUG] Basemap not showing (immediately) on login #1627

tenda1-wbm opened this issue Oct 6, 2024 · 0 comments

Comments

@tenda1-wbm
Copy link

tenda1-wbm commented Oct 6, 2024

Who notified us about the bug?

Tendai Mbwanda

Describe the bug

By design, the platform loads the Drought hazard type when a user logs in. The basemap does not load immediately when this happens, only a blank map canvas is displayed. After switching to another hazard type (Heavy Rain/Floods) then returning to Drought, only then is the basemap loaded. Even when the basemap becomes visible, the progress indicator displayed above the map element remains active as though some background process is still running. The above applies to Uganda, but similar behaviour occurs for Kenya and Zimbabwe.

To Reproduce

Steps to reproduce the behavior:

  1. Login on the IBF platform
  2. Hazard type Drought selected by default, observe the map canvas (no basemap displayed)
  3. Switch to another hazard type (Heavy Rain/Flood)
  4. Observe map canvas (basemap now displayed)
  5. Switch back to Drought (basemap now displayed)

Expected behavior

When the user logs into IBF and lands in the Drought hazard type, the basemap should be displayed immediately.

Screenshots

Uganda

Image

Image

Image

Kenya

Image

Image

Image

Zimbabwe

Image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Firefox 128.0.3 (64-bit)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant