Pega IAC 62sp2 gadget not rendering correcly on IE9 standardmode
We are trying to embed a Pega IAC 62sp2 gadget onto an angular JS application.The angualr JS page will render only on IE9 standard mode and won't run on QuirksMode. Based on the various article on PDN ,62Sp2 IAC gadget will render only on Quirks Mode.We are having issues with buttons and dropdowns while rendering the gadget. Please let me know if it is a technology constraint or any fixes are there to run it on IE standarad mode. SR-A19311 has been opened for this but looking for more information on this set up.
SCRIPT438: Object doesn't support property or method '_initError' pega_tools_xmldocument_1347403921.js!csvalid_13145023181.js!pega_validators_13568956141.js!input_formatter_11228896900.js!!.js, line 1 character 324
That is correct. 6.2 SP2 needs Quirks mode to work properly. There are no fixes to make it work while running in Standards mode. Running in Standards and using HTML5 did not come until Pega 7. That level of effort as you can imagine is far to large to consider bringing back to our legacy PRPC 6 product.
That's correct, after IE9, IE no longer supported running in two different document modes. So IE11 will have the same issue, and in fact be worse for you. It certainly will not be able render your IAC gadget properly with that doctype defined and the explicit meta tag forcing the latest standards. Even without that, by default IE11 is going to run in Edge anyways.
So any attempts at getting this to work in IE9 will be wasted effort if you have plans to move to IE11 (especially since Microsoft has stopped supported IE9).
Once you move to IE11 you will have other compatibility issues for your legacy PRPC release, independent of your IAC configuration.
Honestly you will have much less of a headache if you start planning your Pega 7 upgrade now with all of these cards stacked against you.
Does Pega 7 supports Browser Type: Compatibility in IE 11 for End User Portals ?
We have group user policies which enforces the IE to render in Compatibility mode, and there's no provision for users to switch the mode as the policies are dictated across the board by the networking team. I believe the reason for doing this is to support multiple other applications.
But honestly, now that IE11 has introduced Enterprise mode, your IT department should be migrating to that option It has the ability to granularly set which specific sites will render as IE8, and then you can leave your Pega 7 application alone and run it natively in Standards.
If you have more questions regarding this, I would suggest starting another thread to maintain Dinu's original topic.