I have an dev 1.18 app that allows users to click on features and see various attributes that open in a sidebar (no popus). When you click on the features they highlignt as expected. One click can select features from several different layers.
Now if the user opens the Near Me widget it automatically assumes that one (i think the first one) of the selected features is one it should do the near me analysis on and goes ahead and fires. I think it should wait until I use one of the input methods I have selected before it fires. If I use the "trash can" in the near me widget it does clear things correctly and then behaves as expected.
I have tried putting the near me in a widget controller, in an accordion, and in a fixed panel. None of those options appear to stop the near me from firing if something was previous selected.
The identify strategy (resulting in highlighted / selected features) I am using is from this custom widget: https://community.esri.com/t5/experience-builder-custom-widgets/identify-for-experience-builder-1-14...
I suspect there is something in there that acts just like a click on, say, the point input feature for the near me widget, but that is just a guess. Even if it is true, the near me widget should not fire upon opening. I have the "activate when widget opens" set to none.
I could solve this if there was a "Clear Selected" widget of some sort, but I dont see one.
I love the identify-custom widget so I dont want to stop using it, but it may come with this issue.
Any ideas on a clear widget or how to stop this near me behavior?
