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

Possible bug in toggling lowest ranked Layer List layers #56

Open
AdrianCT opened this issue Aug 24, 2016 · 2 comments
Open

Possible bug in toggling lowest ranked Layer List layers #56

AdrianCT opened this issue Aug 24, 2016 · 2 comments

Comments

@AdrianCT
Copy link

Hi, thanks for developing this widget. I've recently had an issue with clicking the toggle boxes for the lowest ranked group layers in the Layer List of my web app, so in a layer list structure like this:

  • Group Layer 1
    • Sub layer 1a
    • Sub layer 1b
  • Group Layer 2
    • Sub layer 2a
    • Sub layer 2b
  • Group Layer 3
    • Sub layer 3a
    • Sub layer 3b

When trying to toggle sub layers 3a and 3b (the lowest ranked layers), there's no response in the check box on or off when selected. The layer disappears when toggling 3b off, if it's visible upon first page load however the user is unable to have it appear again without reloading.

@slead
Copy link

slead commented Nov 25, 2016

I have exactly the same issue.

It's really hard to debug as there is no error thrown - the checkbox simply fails to respond. Looking at the DOM elements, I can't see any obvious difference between a layer which works and a layer which fails.

A quick workaround is to add a "dummy" layer below the last layer that you need to use - after this the checkbox magically works for the second-last layer.

@slead
Copy link

slead commented Nov 28, 2016

I wonder if this is related? Steps to reproduce:

  • create a brand new web app
  • enable the Local Layer widget, which contains sample layers
  • delete all sample layers
  • open the Layer List widget

Note that one layer remains in the Layer List widget:

ll widget

This layer is removed if you hit Save then reload the map, but could there be a bug somewhere which is causing a "phantom" layer to persist, and which manifests itself as a layer which doesn't obey the Layer List widget controls?

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

2 participants