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

Inconsistent layer behaviour #11

Open
szczz opened this issue Jul 4, 2024 · 3 comments
Open

Inconsistent layer behaviour #11

szczz opened this issue Jul 4, 2024 · 3 comments
Labels
in DevOps This issue has been migrated to DevOps URGENT This needs to be addressed ASAP and before release

Comments

@szczz
Copy link
Member

szczz commented Jul 4, 2024

Describe the bug
In some cases the temperature (?) layer displays when maximum temperature is disabled and in other cases it doesn't

Displayed:
image

Not Displayed:
image

To Reproduce
Steps to reproduce the behavior:

  1. Select the CMIP6 dataset
  2. Select the 2021-2050 time period
  3. Switch to Minimum temperature
  4. Notice the layer is disabled in the legend but the layer remains
  5. Switch back to Maximum temperature
  6. Notice the layer is disabled in the legend but a layer remains (don't believe this is the maximum layer)

Expected behavior
Honestly not sure, assuming it shouldn't display when disabled

Additional context
Updated with steps

@spencerwahl
Copy link
Member

Cannot reproduce

@szczz
Copy link
Member Author

szczz commented Jul 4, 2024

Cannot reproduce

Updated the steps to reproduce

@spencerwahl
Copy link
Member

Reproduced, issue with what layer the legend is tracking on variable, etc. change. It is showing the layer as unchecked because its tracking the "rightmost" time slider layer and showing a different one on the map.

@dan-bowerman dan-bowerman added URGENT This needs to be addressed ASAP and before release in DevOps This issue has been migrated to DevOps labels Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in DevOps This issue has been migrated to DevOps URGENT This needs to be addressed ASAP and before release
Projects
None yet
Development

No branches or pull requests

3 participants