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
Small issue, but noticed some different behaviour between Bing Streetside and Mapillary.
If you click on a Mapillary marker to open an image, then select an OSM object or even move your mouse away the yellow highlight disappears. It only reappears if you mouse over a Mapillary trace again.
This does not happen with Streetside or OSC, where the selected image is always highlighted in yellow. Makes it much easier to see where the image is on the map, and where it's pointing.
Occurs in both Firefox and Chrome (Windows10).
The text was updated successfully, but these errors were encountered:
I've managed to fix persisting the highlight when selecting an OSM object then deselecting it.
However, on further testing I've found that if multiple street imagery layers are active at once they do not interact nicely at all:
Selecting a bubble then enabling a second imagery layer removes the hovered and selected highlighting
Selecting a bubble then disabling a second imagery layer deselects the bubble
If multiple imagery layers are enabled and you select a bubble it only temporarily becomes highlighted
If multiple imagery layers are enabled and a bubble is highlighted, hovering over another imagery layer's bubble will remove the selected and hovered highlighting
Small issue, but noticed some different behaviour between Bing Streetside and Mapillary.
If you click on a Mapillary marker to open an image, then select an OSM object or even move your mouse away the yellow highlight disappears. It only reappears if you mouse over a Mapillary trace again.
This does not happen with Streetside or OSC, where the selected image is always highlighted in yellow. Makes it much easier to see where the image is on the map, and where it's pointing.
Occurs in both Firefox and Chrome (Windows10).
The text was updated successfully, but these errors were encountered: