Customer observed CMS pages got garbled (possibly in v3.5). As per customer clarification, HTML META elements had difference between those two versions as following. (A) v3.1 : <meta http-equiv="X-UA-Compatible" content="IE=edge"> (B) v3.5 CR9 : <meta name="X-UA-Compatible" content="IE=edge">
Here is a couple of questions. (1) what caused this difference ? Is this a bug or spec? (2) Is it possible and allowed to modify Apache httpd.conf on the META element to resolve the problem ? <meta http-equiv="X-UA-Compatible" content="IE=edge">
Environment
Release: Component: APIPRD
Resolution
1) CR9 has a defect where the X-UA-Compatible was not properly set. It is resolved in CR10.