I have a web application that incorporate an infoTemplate (esriPopup)
when the user clicks on a road feature in the map. This works fine in the main map, but I have additional maps that compare 2 preloaded scenario maps. When the user zooms in to one of the scenario compare maps, they should be able to click one of the road features and the infoTemplate
is displayed. What I am noticing is there is a slight offset of where the user has to click in order to get the infoTemplat
e to display properly. In other words, the user has to click slightly above the feature layer in order to select it and trigger the infoTemplate
to display correctly. If the user click directly on the road feature, it displays "No information available".
It's a .NET
application with most of the client side functionality in an AMD-style
main.js file. There is an esri.css and Style.css that controls most of the styling. I am refactoring the application and am having trouble even determining where the issue originates from (is it the cursor, the infoTemplate
, or the roadsLayer
settings?)
The infoTemplate for the scenario compare maps looks like this:
it = new InfoTemplate("Feature Info");
it.setContent(lang.hitch(map,generateInfoContent));
its = {};its[idx] = { infoTemplate: it, layerUrl: null }
map.getLayersVisibleAtScale()[1].setInfoTemplates(its);
The method .getLayersVisibleAtScale()
seems to be an esri
method of class map
but I have no clue why this would produce a slick offset in selecting the layer. Any ideas as to how to resolve this?