Applies to Pega Platform 7.4-8.6

Learn how to resolve issues with browser alerts and prompt boxes that are blocked by the Google Chrome 92 browser.

Symptoms

Explanation

Solution 

Symptoms

Built-in browser alert messages and prompt boxes that are triggered by an action on the User portal do not display after updating to the Google Chrome 92 browser. This occurs on using Pega mashups that are hosted in third-party domains and on Pega applications embedded in Salesforce domain.

Explanation

Google Chrome 92 browser prevents cross-origin iFrames (iFrames with origin that is different from the top-level page) from triggering prompts such as window.alert, window.confirm, window.prompt, and so on. This behavior prevents embedded pages to spoof the users to believe that the message is displayed by the website or the browser.

Visit the Google Chrome Enterprise Help Center to learn more from the posts that discuss the changes introduced in the Google Chrome 92 update. Also visit the Chrome Platform Status website to learn more about Feature: Remove alert(), confirm(), and prompt for cross origin iFrames.

Solution

Any of the following approaches resolves the issue:

• Add the following command line flag to your Chrome shortcut:
  --disable-features = "SuppressDifferentOriginSubframeJSDialogs"

• Set the SuppressDifferentOriginSubframeDialogs registry item or preference to False based on the Operating System.

• Revisit your application code to review instances where you rely on native prompt and evaluate if they can be converted to Pega modal dialogs.

• Revert to an earlier version of the Google Chrome browser.

• Use a proxy configuration in which the web server that hosts the top-level application sends proxy requests to the Pega servers.
  For example, the https://clientsite.com/ top-level application embeds the Pega web mashup https://clientsite.com/prweb/ client web server proxy in https://<client_env>-.pegacloud.net.

For information on troubleshooting issues with Pega mashup that are caused by browsers blocking third-party cookies, read Troubleshooting Pega mashup issues caused by bowsers blocking third-party cookies

Note

• Windows registry location: Software\Policies\Google\Chrome\SuppressDifferentOriginSubframeDialogs

  • Example: 0x00000000

• Mac/Linux preference name: SuppressDifferentOriginSubframeDialogs

  • Example: false

• Android restriction name: SuppressDifferentOriginSubframeDialogs

  • Example: false