We have had a web app builder app set up for a few years now and working fine. In the map we have two layers that are the same feature, but one is our editing layer and the other is sorted and symbolized differently as our viewing layer. The editing layer is symbolized, but we have the transparency set to 100%. In the past this worked just fine, meaning that end users would select the point and the "selection halo" would appear. staff would then move the dot and enter info as needed, none the wiser that they hadn't moved the viewing layer. An end user reached out to tell me that they were no longer able to select the points- but what I figured out is that because the transparency on the edit layer was turned up to 100%, the selection color is now also set to 100% transparency. Technically, you can still move the point, but you don't know you have it selected so you have to go off of the fact that the mouse pointer turns into the little pointing finger and then move things around. what am I missing here? I swear this used to let us see the selection regardless of the transparency of the point!? (I have tested in both map viewer class and map viewer, we are using Smart Editor widget in the Web App Builder Developer Edition with data that is not hosted in AGO).
