You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we've outgrown the default Layers UI that ships with Leaflet. It's also a bit confusing the way it currently labels and orders the map layers:
We could of course update the layer names, but overall I think it would benefit from some minor design improvements, e.g. making the separation between housing justice actions & emergency protections more clear (@bretthalperin feel free to weigh in on this!)
If we made this its own component it would likely have the additional benefit of making it more straight forward to do lazy loading of map layers.
The text was updated successfully, but these errors were encountered:
agreed it is not functioning as intended based on usability test findings. could we start rolling out the new design for this? not sure how we should go about the re-design in general, but hope to talk more concretely about that today.
I think that’s a possibility, let’s chat about it more
On Mon, Jun 1, 2020 at 6:19 AM bretthalperin ***@***.***> wrote:
agreed it is not functioning as intended based on usability test findings.
could we start rolling out the new design for this? not sure how we should
go about the re-design in general, but hope to talk more concretely about
that today.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHPVGADCDXXFVYXU6OC4DRUOTERANCNFSM4NPPVIMA>
.
I think we've outgrown the default Layers UI that ships with Leaflet. It's also a bit confusing the way it currently labels and orders the map layers:
We could of course update the layer names, but overall I think it would benefit from some minor design improvements, e.g. making the separation between housing justice actions & emergency protections more clear (@bretthalperin feel free to weigh in on this!)
If we made this its own component it would likely have the additional benefit of making it more straight forward to do lazy loading of map layers.
The text was updated successfully, but these errors were encountered: