topic Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser in ArcGIS JavaScript Maps SDK Questions

Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Mon, 29 Mar 2021 18:32:31 GMT

- Javascript API 3.28

- Chrome 89.0.4389.90

- https://www.bcpao.us/PropertySearch/#/account/2961057

---------------------------------------------------------------------------------------------------

Our public Javascript API 3x web map (“MapView”), in production since 2016, started intermittently failing to fire the map.on(“click”) event in Chrome browser on Windows 10 desktop for some users when inside an iframe. Other elements within the map (checkboxes, buttons, input, search, zoom, pan, layer toggle, etc.) all work. I can detect that map_gc is the event target every time, but map.on(“click”) doesn’t always fire. I tried loading the web map into a div instead of an iframe, but the result was the same. When the map is loaded in its own window, it seems to work every time. There are no errors in the console.

The website, map, and all resources are local on a single server. There is another iframe in a separate tab under the web map tab that contains a Pictometry/Eagleview IPA image viewer that initially has no src, so everything is single domain at that point. There is a resize event on the iframe to ensure the map fits inside the tabbed panel as the browser window is resized. Sometimes resizing the browser window fixes or breaks the map-click, and sometimes has no affect. Sometimes it just works and is difficult to break. Sometimes it breaks every time.

This doesn’t happen on all computers and doesn’t appear to happen in any other browser (Edge, IE11, Firefox, Opera, Brave, Safari, etc.) It doesn't seem to happen on a tablet (Android or Apple) in Chrome either.

To see this in action, from the URL included above, click the MapView button above the photo. Maybe I’ve stared at it too long to see an obvious issue . . .

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Mon, 29 Mar 2021 13:30:11 GMT

Hey DanDan,

We noticed last Thursday one of our users running into the exact same issue that you are describing. We also use the 3.28 API and your Chrome version is the exact same as well. One small difference is we have our Map setup in Div tags. I was able to click on the map within your website and it worked for me fine, but when I had the user that is having issues click it, he couldn't get it to work.

One thing we noticed is that the Map Click event refuses to trigger, but will eventually trigger after several clicks. It works one time, then goes back to broken state until so many clicks are hit again. This happens both in our environment and also on yours for that one user. We also noticed if we point to a new version of the API (3.35) it fixed the issue for the user. We don't want to go that route just yet, but I did want to point it out.

Please let me know if you are still working through this issue or if you were able to come up with a solution.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Tue, 30 Mar 2021 12:33:38 GMT

Greetings, and thank you for contacting me. I upgraded to 3.35 in our test environment, and that seems to have solved the issue. I haven't been able to get the map click to fail today since upgrading to 3.35. We are receiving more frequent reports of this issue, so I'm implementing faster than I usually would. I don't yet know the cause of this issue, but I wonder if there is a low tolerance in the API for differentiating between a pan and a click. Some users with mice set to fast movement tend to have a harder time clicking because the slightest movement of the mouse causes a pan rather than a click. I don't know if Chrome is doing anything to exacerbate this issue but upgrading the JSAPI to 3.35 seems to solve it. Thanks again. -Dan

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Mon, 29 Mar 2021 17:17:22 GMT

Upgrading to JSAPI 3.35 seems to have solved this issue and is implemented. My thanks to those who provided suggestions.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

HenryKo2 — Tue, 30 Mar 2021 07:00:38 GMT

Hi all, we started to face similar issues last few weeks, where a small number of users are unable to draw geometries on the map with mouse-clicks. We are using JSAPI 3.22. MS Edge doesn't have this issue, but Chrome does, and only for some users. But with the same Chrome version, it works for most users. This issue started to spread to more and more users gradually. We use DIV, no iFrame.

We are a large corporate and initially we suspect it's something to do with user policies/settings. But at the moment, this does not appear to be the case.

We upgraded Chrome to a latest beta version, no luck. But another user downgraded her version (I don't have the specifics here), and it started to work for her again.

We are still investigating, and will post here for any further progress (e.g. change JSAPI versions).

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Tue, 30 Mar 2021 10:37:04 GMT

We have Edge, Edge Chromium, Firefox, and Chrome, only Chrome fails for our user. Just like HenryKo2 states, we have had several other users with the same Chrome version do Map Clicks and it works for them, but a small set of users continue to fail.

We also thought it could be a user policies/settings thing once our user was able to fail on two different computers. Unfortunately due to teleworking in place, it's hard to for us to test that on more computers at the current moment for us.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Tue, 30 Mar 2021 11:44:44 GMT

Thank you. Although upgrading to JSAPI 3.35 seems to solve the issue, i sure would like to know the cause, and why it is intermittent and only affects some users.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Tue, 30 Mar 2021 11:46:04 GMT

I want to add that even though updating to 3.35 API is a solution, I want to find an alternative solution since upgrading currently breaks several other tools for our application.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Tue, 30 Mar 2021 12:01:41 GMT

Fortunately, that wasn't the case for us, at least not yet. What other types of tools does upgrading to 3.35 break?

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Tue, 30 Mar 2021 12:11:04 GMT

We upgraded our API about 2 years ago and found anything above 3.28 would break ESRI's Draw widget due to it not using something called _tGraphic. It essentially allows a preview of Draw tools on the map before placing the graphic down and we also custom made that graphic to show on the fly measurements. There could have been other tools that broke, but we stopped testing when we saw that and began testing with 3.28, where everything worked.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Wed, 31 Mar 2021 12:36:43 GMT

Just an FYI that I struggled to find a solution for this all last week and planned to try an API upgrade on Monday as a last ditch hope that it would solve it. I went so far as to build a very basic two-tab page with the same two maps (JSAPI 3.28 and Pictometry) populating two iframes. It worked every time, so I started to think it may be some other resource in my production app that was interfering with the JSAPI. I almost never post on blogs but I'm glad I did. I received a private message very soon after from a developer who was experiencing the same issue who later confirmed that upgrading to 3.35 worked for their applications. My thanks to that person as well for being the first to respond and to give me hope that upgrading to 3.35 was a viable option. One thing you will notice with the 3.35 upgrade is that map clicks happen much faster than in 3.28. In my application, since upgrading to 3.35, map clicks respond now in less than 100ms where before it would take around 700ms.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

HenryKo2 — Tue, 30 Mar 2021 21:33:51 GMT

I forgot to mention about the other test we did. The issue happens for one user. So we had another user log in to her laptop, and it worked for the second person. Same Chrome. We exported their Chrome profiles (with the command chrome://policy) and compared, did not see anything that could cause the issue. I'm starting to think it could be a combination of things.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Tue, 30 Mar 2021 21:41:49 GMT

Has anyone noticed if they are able to fix/break it by resizing the browser window? When it worked, I could maximize the browser window, which would break it, but when I restored the browser window to it's original size (clicking the browser buttons), it would work again. In this scenario, it would exhibit consistent behavior.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

HenryKo2 — Wed, 31 Mar 2021 00:04:57 GMT

Just discovered this: this issue exists for me on my main monitor, 2560x1440 at 125%, but as soon as I dragged Chrome to my laptop screen, 1920x1080 at 100%, the issue went away! Dragging back to my monitor causes the issue to happen again. I'm on Windows 10. So, along with the window size, this seems to imply JSAPI bug (but doesn't explain why it only started happening recently even though we used the same JSAPI). Maybe the JSAPI bug surfaced with recent Windows updates?

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Wed, 31 Mar 2021 11:22:04 GMT

We attempted the resize concept, but that didn't appear to do anything for us.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Wed, 31 Mar 2021 11:30:04 GMT

That's a very good find on the resolution/zoom. We had our user with the issue try some things and soon as the user adjusted the zoom to anything more than 100%, it would break. Keeping it at 100% fixed the issue. Our entire organization had our Chrome updated to 89.0.4389.90 last week, the same time we noticed the issue occur. I would say it's a combination of Chrome changes along with the JSAPI. Of course, I believe we also had all of our monthly security patches pushed.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Wed, 31 Mar 2021 11:45:06 GMT

This may be an unrelated longshot, but after updating to 3.35, my map.on("click") event fires immediately rather than the delayed action found in 3.28. I found the post below where the developer changed a setting to make the click fire immediately.

https://community.esri.com/t5/arcgis-api-for-javascript/map-click-delay/m-p/720270

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Wed, 31 Mar 2021 12:08:35 GMT

Also, please see the post below where click event for popup not working. They, too, mention screen resolution.

https://community.esri.com/t5/arcgis-api-for-javascript/no-popup-info-in-chrome/m-p/1041781

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

BenjaminCumberland — Wed, 31 Mar 2021 12:11:05 GMT

We put the user back to a broken state and tried to set the "map.navigationManager.setImmediateClick()". It remained in a broken state, thanks for the idea though.

Re: Javascript API 3x Map Click Event Intermittently Fails to Fire in Chrome Browser

Dan — Wed, 31 Mar 2021 13:45:54 GMT

I confirm that my 3.28 test app mentioned previously that "worked every time" indeed fails every time if the browser scale is set to anything but 100%. This may have something to do with how JSAPI handles pixel interpolation in Chrome. I recall many years ago when IE was king that browser scale <> 100% broke our long-retired1990s ESRI MapObjects map. Strange to see it happening again.