topic Re: [JSAPI 4.8 vs 4.7] Popup empty after switching map in ArcGIS JavaScript Maps SDK Questions

[JSAPI 4.8 vs 4.7] Popup empty after switching map

QiZhao — Sun, 12 Dec 2021 07:14:55 GMT

I'm updating my app to use latest v4.8 JSAPI, while I found a potential bug of the API. In my application, user can switch different webmaps without refresh the page. However, after switching the webmap once, the popup window of the webmap become empty.

This issue does not exist in v4.7 API.

The issue only happens after changing "map" of a "view".

//change map
view.map = new WebMap({
  portalItem: {
    id: "f2e9b762544945f390ca4ac3671cfa72"
  }
});‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

If I create the view with WebMap in constructor, everything works fine. See the code below.

//do not change map
view = new MapView({
  container: "viewDiv"
  map: new WebMap({
    portalItem: {
      id: "f2e9b762544945f390ca4ac3671cfa72"
    }
  }),
});‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Here is a running example:

https://codepen.io/anon/pen/RBwqjz

Steps to repeat the issue with this example:

Wait for the page fully loaded
Click "Switch Map" button
Wait for the new Web Map fully loaded
Click any graphics of the Web Map
The first popup should look fine
Close the popup
Click any graphics, then the popup will be all empty

Re: [JSAPI 4.8 vs 4.7] Popup empty after switching map

ReneRubalcava — Wed, 11 Jul 2018 02:10:26 GMT

Just to verify, this is happening for me in Edge and Firefox on Windows. But Chrome is ok. Is that the same for you?

Re: [JSAPI 4.8 vs 4.7] Popup empty after switching map

QiZhao — Wed, 11 Jul 2018 14:50:15 GMT

Hi Rene,

Thanks for your quick reply. Below are the browsers in which I saw the issue:

Chrome v67.0.8896.99 64-bit
Chrome v66.0.3359.170 64-bit
Microsoft Edge v42.17134.1.0
Firefox v61.0.1
Firefox v60.0.2

All the browsers mentioned above are in Windows 10 v1803 x64.

Let me know if you need additional info. Thanks.

Re: [JSAPI 4.8 vs 4.7] Popup empty after switching map

QiZhao — Fri, 28 Sep 2018 14:55:11 GMT

This issue has been fixed in v4.9 API. Thanks.