Possible bug in toggling lowest ranked Layer List layers about locallayer

[slead]

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]

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:

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?