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 was playing around on Atlas and it looks like the "What's Here" feature doesn't work on non-private land when you have the Land Ownership layer turned on. With that layer off, I can click somewhere in a National Forest, or State Park, or similar and get info. However, when I turn Land Ownership on, it doesn't seem to register that I've clicked. It's almost like that layer is "intercepting" the click (maybe because it's the topmost layer?)
Browsers
Chrome
Safari
Firefox
Brave
Microsoft Edge
Internet Explorer
Other
Reproduction steps
Turn on Land Ownership
Click on the Mt Timp summit
Turn off Land Ownership
Click on the Mt timp summit
Developer console logs
Console log doesn't log any requests when clicking on a location covered by the Land Ownership layer.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Good catch. The hit test is running on the vector layer and expecting a popup to show up instead of doing the identify. This logic was intended to not identify when selecting a geocode or sherlock match graphic.
Is there an existing issue for this?
Current Behavior
I was playing around on Atlas and it looks like the "What's Here" feature doesn't work on non-private land when you have the Land Ownership layer turned on. With that layer off, I can click somewhere in a National Forest, or State Park, or similar and get info. However, when I turn Land Ownership on, it doesn't seem to register that I've clicked. It's almost like that layer is "intercepting" the click (maybe because it's the topmost layer?)
Browsers
Reproduction steps
Developer console logs
Console log doesn't log any requests when clicking on a location covered by the Land Ownership layer.
Additional information
No response
The text was updated successfully, but these errors were encountered: