Support Article

X-UA-Compatible META tag in Pega generated UI is still IE 5



A developer has noticed that Pega generated HTML contains the following
<meta http-equiv="X-UA-Compatible" content="IE=5">

Where did this come from?
Why is Pega using such an old standard?

Error Messages


Steps to Reproduce


Root Cause

You are seeing this due to installing the IE10/11 compatibility HFIXs mentioned here:


Prior to Pega 7, PRPC requires quirks mode to render properly. The purpose of the compatibility mode HFIXs is to instruct newer modern browsers to render our document in Quirks mode. Without this, the browser defaults to standards mode which can cause various UI issues.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Have a question? Get answers now.

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