nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IE 11

BFC

Hi, [color=#1f497d;]Is there a problem with Internet Explorer 11 and BVT? We are doing some testing. Our test report displays in Firefox, Chrome, IE8, IE10, but not IE11.[/color] [color=#1f497d;]Thanks[/color][color=#1f497d;]Bob[/color]

Find more posts tagged with

Comments

BFC

I have more information on this issue. Comparing IE 11, and IE 10 We have reports which do not require input parameters from the users.These reports display in IE 10, and IE 11. We have reports which require start and end date parameters.These reports display in IE 10. These reports do NOT display in IE11. The parameter dialogs are not displayed, just the spinner.Log has Jun 03, 2014 9:38:07 AM com.actuate.iportal.utils.Utility getCustomParameterDefinitionsWARNING: A DOCTYPE was passed into the XML document The parameters are type Date. As an experiment I changed to type String, it did not make a difference, the reports do not display in IE 11 If the server IP is added to IE 11 compatibility settings, then the reports with parameters do display.<a data-ipb='nomediaparse' href='http://winaero.com/blog/how-to-enable-compatibility-view-in-internet-explorer-11-ie11/'>http://winaero.com/blog/how-to-enable-compatibility-view-in-internet-explorer-11-ie11/</a> Any ideas? Bob

BFC

This is my solution, if anyone else is having a similar problem. The following line was added to IVStandaloneViewerFragment.jsp. <META http-equiv="X-UA-Compatible" content="IE= EmulateIE10">

The line was added after title and before CHARSET=utf-8. Bob

SamBachman

This issue continues to Edge. To me is seems like the POST request to get the parameters from the report 
<a data-ipb='nomediaparse' href='https://****.com####/iportal/wsservlet?'>https://****.com:####/iportal/wsservlet?</a>
fails because Edge refuses to set the cookie with the skin as requested in the preceeding POST
<a data-ipb='nomediaparse' href='https://****.com####/iportal/loginservlet?'>https://****.com:####/iportal/loginservlet?</a>
<div> </div>
<div> Set-Cookie: skin="treeview"; Expires=Sat, 17-Jun-2017 15:48:52 CDT; Path="/"; Secure; HttpOnly</div>

Clement Wong

Microsoft dropped Compatibility View / Document Mode (<a data-ipb='nomediaparse' href='https://msdn.microsoft.com/en-us/library/dn904497(v=vs.85).aspx'>https://msdn.microsoft.com/en-us/library/dn904497(v=vs.85).aspx</a>) in Edge. 
 
In Microsoft Edge, developer-initiated switching of the document mode via the x-ua-compatible header will be ignored on most Internet sites and they will be rendered with the EdgeHTML engine.
 
At this time, I am not aware of a workaround. iHub 16 SP1 has Edge support.

suresh@anumolu

Clement, 
 
We are using the following BIRT version. Is there anyway can this be fixed for IE11? Even tried adding the following line as Bob suggested. Any help would be appreaciated. 
META http-equiv="X-UA-Compatible" content="IE= EmulateIE10">
 
BIRT Version:
<div>Actuate BIRT Designer Professional </div>
<div>Version: 4.2.3</div>
<div>Build id: v20131216</div>

Clement Wong

Suresh,
 
The commercial version of BIRT you are using, corresponding to the Version/Build is "iHub 3.0".
 
There was an "iHub 3.0 Fix1" release that included IE 11 support (which is more than a simple 1 line change), including a few other fixes and enhancements.
 
Please contact your local support center to get this version. Here's their contact info:
<a data-ipb='nomediaparse' href='http://www.actuate.com/resources/support/global-support-centers/'>http://www.actuate.com/resources/support/global-support-centers/</a>

suresh@anumolu

Thanks for the prompt response. Will there be any comptability issues? We have some customizations in place, we just want to make sure it doesnt break after the fix.

Clement Wong

Generally, there should not be. However, I'm not sure what "customizations" were made in your environment. You may want to confirm with Support.