Anyone else having an issue with IE 11 and Pega 7? We're not able to load pega 7 in a iframe within a portal application when it's IE 11.
I've seen articles on older version of prpc and hotfixes but nothing for Pega 7. I was wondering if anyone else had run into this issue. What browser setting did you need to enable?
Accepted Solution
Cox Communications
US
Looks like it was an issue with the gateway. the frame dom was coming back in most cases however it was 0px in height. we're going to do a contextual forward to our gateway from our load balancer
Hi David,
Tell me more about what is configured here. Reading the terms you are using I am inferring you are using Pega 7 application embedded into your company portal using an IAC gadget or "Web Mashup"
What version of Pega 7 is this?
Are you using a DocType in your top level web portal?
Do you have compatibility view turned on?
----
Pega 7 is designed with Standards mode in mind using the HTML5 DocType. So if your top level portal is also designed with current standards you should not have this issue. If your top level portal or IT settings is trying to force a different/older mode, then that is likely your root cause, because your Pega 7 app will be forced to inherit said mode.
Cox Communications
US
We have the following doctype -
[10/2/2015 8:12 AM] Parks, Patrick (CCI-Atlanta):
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>
we're running in 'document mode 5' from a group policy
we're launching a page that has javascript to reach out to the pegacloud gateway.
that page ends up blank.
Hi David,
I am more concerned with running in the IE5 document mode, as that is Quirks, and will cause you problems in Pega 7, with or without Web Mashup involved.
But you are also correct that violating same-domain origin policy can cause a blank frame. However, I would expect you to have this issue with other IE versions as well, and not have it be specific to IE11.
Accepted Solution
Cox Communications
US
Looks like it was an issue with the gateway. the frame dom was coming back in most cases however it was 0px in height. we're going to do a contextual forward to our gateway from our load balancer