There is a text labeling oversight in the Map Layers widget. The text for the Show or Hide Labels option is static and displays Hide Labels at all times regardless of the state of the labels. This can be confusing to the user. Ideally, this text would be tied to the state of the labels and read Show Labels if the labels are currently off and would respect if the label state was changed from the Map Layers Widget or any other source. A simpler change would be to change the text to Show/Hide Labels or Toggle Labels.
This looks more like a bug. The designed behavior is to show the action that is about to happen.
However, when I tested it on the AGOL environment - it showed the expected behavior:
I also put it in a Widget Controller and the behavior is still as expected.
I am not sure why you see the behavior in the above screenshot. What is the environment/version? Is it possible to provide me a sample or data? Thanks
Okay, per further testing, it might be the following case -
When there are multiple layers that can show or hide labels, and you already opened them, then the layers beneath the first one will show this problematic behavior;
If there is only one layer, or you only operate on the first available layer (regarding this feature), the behavior looks fine.
We will take a look to fix it. @JeffreyThompson2 Let me know if your app is not configured that way then we can dig further. Thanks
The screenshot is from ArcGIS Online. Here is the Experience.
The first labeled layer in the map ParksAmenity > Monument Art shows the correct behavior. All lower layers do not change text. The BaseMap-Council District (Production) layer shows the incorrect behavior regardless of whether or not the ParksAmenity layer has been interacted with.
I observe the same behavior in Developer Edition 1.12.
@JeffreyThompson2 The previous behavior has been fixed with the latest AGOL release and should work fine now. Thanks
@TonghuiMing Will the SSO bug be fixed in Developer Edition 1.14?
@JeffreyThompson2 Yes, it will be picked up by the upcoming 1.14 as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.