nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Popups Not Opening in Chrome When WAB App Embedded in Iframe

JamesMadden1

I have a WAB app that I built using the developer edition version 2.13. I've been working on the app for about a year now and we recently noticed that the feature popups no longer open in the app we have embedded it in. The app is embedded through an iFrame. Our organization supports IE, Edge and Chrome internally and everything works fine with the microsoft browsers but no click events are triggered in chrome. It's odd though because the double click event on the map still works with the zoom functionality. I also created a test app where I embedded the wab app. I placed copies of the test app on our primary dz web server and also on our internal web box. The popups work on the internal box in chrome as expected. The popups only render in the dz server when the test app is accessed over http - https does not work. Our chrome software recently got updated to version 89.0.4389.90. I reverted my chrome back to version 84 the other day and everything began to work again as expected. A nightly routine updated my chrome overnight back to version 89.x and the popups stopped working. The popup issue appears to effect all our portal apps and maps.

So the issue appears to be related to our domain and browser. Has anybody ran into similar issues with WAB apps or Portal maps? The iFrame code is shown below.

Find more posts tagged with

Accepted answers

JamesMadden1

I was able to resolve the issue by upgrading to WAB 2.19. The popups now work properly in iFrames. The issue appeared to effect all our web maps (Portal 10.7.1) and all our custom WAB apps (2.13).

All comments

JamesMadden1

I was able to resolve the issue by upgrading to WAB 2.19. The popups now work properly in iFrames. The issue appeared to effect all our web maps (Portal 10.7.1) and all our custom WAB apps (2.13).

IngridMans

How do you think this would relate if we have an app built in the browser built-in version of WAB? I found this post because I have recently had complaints about a layer's popups not appearing in Chrome, on a WAB (built-in) app I created on our Portal (10.8). The service is a referenced map service sourced from our federated server. The only common denominators seem to be popups not consistently working for Chrome users on laptops or tablets, using a wifi network (both inside our org and outside customers). I've yet to experience the behavior myself from my own workstation.

JamesMadden1

The issue we were seeing appeared to effect all our wab apps (custom and built-in) and portal web maps when embedded in iFrames. However, the issue only appeared in Chrome and it was domain specific. We have one server that sits in a dz and accepts requests from the public internet. The other is only available internally. I created a quick test app and placed iFrames in each that pointed at a portal app. The popups showed on the internal box but not in the dz server. The popups were working in Chrome before the recent updates Google posted.

Our Portal is running at version 10.7.1. The layers with the popups are map services.

I have Google Chrome on a personal machine that is running the same version as my organization. The popups worked with WAB 2.13 on my personal machine. I tried reverting my chrome version on my company machine and that worked until a nightly routine pushed me back to 89.x. ESRI reported that they are getting a lot of calls in regards to chrome and they believe it has something to do with user profiles not being setup correctly. The resolution we found involved updating our local wab app to version 2.19. I understand that isn't really an option for larger orgs with many apps, so maybe you should start a case with ESRI.

IngridMans

Thanks for that feedback. Silly question: if my apps were built using the non-developers edition of WAB, then how do I update those?

Banff_GIS_Department

I have the same problem - built-in WAB and not all users are suffering the no-popup situation. It only happens in Chrome (all seems to be on latest version 89.0.4389.90). I am using Portal 10.7.1, federated server.

JamesMadden1

I would contact esri tech support over chat and request a case if you have a maintenance agreement with them. Our organization pushed chrome updates about a week ago and another esri thread mentions they think there is an issue with the chrome profiles. Our issue had me very puzzled as the same source code worked from our internal domain but not from our public facing box.

Dan

Same issue with the Javascript API: Intermittent, only in Chrome, and only for some users (although spreading to more users). We, too, solved it by updating the API, but still looking for the actual cause. You may want to follow this thread as well.

https://community.esri.com/t5/arcgis-api-for-javascript/javascript-api-3x-map-click-event-intermittently-fails-to-fire/m-p/1040738#M72210

IngridMans

Is there a post for dummies like me about how to upgrade the JS API? Out apps were built using OOTB WAB rather than developers edition.

Brian_Wilson

We've been yapping about it on this posting Re: Web app not working on chrome

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.