Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega platform renders differently on different browsers



Pega platform renders differently on different browsers i.e. Chrome, Internet Explorer (IE) and Edge browsers. User is unable to work on Chrome and Edge browsers.

The below issues occur:

  1. Single Sign-On (SSO) URL does not open on the Chrome and Edge browsers and renders a blank screen
  2. Sections are blank on the Chrome and Edge browsers
  3. Unable to create any rule on any browser

Error Messages

!STANDARD:23 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-wjgX45GGmGfX8+pRt5Um+t0m/whb9O1exlXlMpSWdXc='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

Steps to Reproduce

  1. Change the policy name in the application definition 
  2. Uncheck Unsafe Inline and Unsafe Eval
  3. Add the response headers to the Dynamic System Setting (DSS) setting

Root Cause

An issue in the custom application code or rules.


Perform the following local-change:
  1. Enable Unsafe Inline and Unable Eval on policy name in the application definition

  2. Remove the double inverted comma from the CSP (Content Security Policy), "Content-Security-Policy":default-src 'self', in the http/responseHeaders Dynamic System Setting (DSS)




Published April 11, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us