OnMouse Events disable OnClick event for FeatureLayers

Question

Start with the sample application here:

http://help.arcgis.com/en/webapi/javascript/arcgis/help/jssamples_start.htm#jssamples/fl_hover.html

Add the following code at the bottom of the init function:

dojo.connect(southCarolinaCounties, "onClick", function(evt) {
                                                                window.location = "http://www.esri.com"
                                                });

Notice that the onClick event does not respond to mouse clicks. Now comment out the southCarolinaCounties "onMouseOver" event and notice that now the onClick event works.

I have tested this with a few of the onMouse events and all seem to disable the onClick event. How can I have both an onMouseOver and an onClick event for a feature layer?

JonathanCruz1 · Answer

Thanks for your post Luke! By removing my highlighted graphic, I can execute both the "click" & "mouse-over" events on a single point graphic.

LukeRogers · Answer

I can't see that this is a bug, unless I'm missing something?!

See my response here

The highlightGraphic is being added on top of the southCarolinaCounties layer thus masking it, so it is the highlightGraphic that will get the click, unless you expect the click to penetrate through to any 'lower' layers?

For me this is totally expected behaviour, for it to work any other way would be very odd!

...and this is exactly where ESRI Tech Support landed too. In hindsight that makes sense. The onClick event can only be handled by the top graphic, whatever that is, and it is handled at the map.graphics layer level and not on specific graphic features.

Here's the latest from ESRI to close out this thread:

The 'onClick' event does fire if the FeatureLayer implements both 'onMouseOver' and an 'onClick' events simultaneously. I have attached the modified application in the email in order to demonstrate the behavior.

The issue was earlier encountered due to the application workflow as explained below. (The events do work correctly.)

The problem with the original test case is that a graphic is added to the map each time when the mouse is hovered over a feature. This graphic is used to highlight the feature. Thus, when users click on the highlighted graphic you'll need to listen for the map.graphics onclick event instead.

You may note that, if the highlighted graphic is not added to the map, the events will work correctly.

flEvents.html.txt.zip

__Rich_ · Answer

I can't see that this is a bug, unless I'm missing something?!

See my response here

The highlightGraphic is being added on top of the southCarolinaCounties layer thus masking it, so it is the highlightGraphic that will get the click, unless you expect the click to penetrate through to any 'lower' layers?

For me this is totally expected behaviour, for it to work any other way would be very odd!