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; } } }

Charts give error resizeSVG is not defined

hallj05

Hey, we are using Open Source BIRT version 4.4.1 and are using the BIRT viewer tag library to display reports in our web app. BIRT is deployed on the same server as our app.
 
When we run reports that have a chart with an output type of SVG then we get the following error. (This was working before) I can change the output type to something else and it will display correctly in Chrome, but not in IE. I need it to work in IE, which the version that I'm using is IE11.
 
 
Here is the error that shows up in Chrome for this.
Uncaught ReferenceError: resizeSVG is not defined
 
 
Any idea as to why this error has started to happen or how to fix it so that charts display using SVG.
 
Thanks!

Find more posts tagged with

Comments

Clement Wong

I have OS BIRT 4.4.2 and am able to view reports with an SVG charts in IE 11 and Chrome, when generated from the Designer.
 
Are you able to test a simple report with SVG from the Designer using the same problematic browsers?
 
So SVG used to work before in both Chrome and IE 11 until recently? There appears to be other factors that would cause this.
 
You mentioned that you are using the BIRT Viewer Tag library, what does your HTML page look like? Did you make any changes there? Do you have a DOCTYPE declaration. If so, what is it?
 
Did you change your underlying app server, or upgrade it?
 
Is that error you referenced from Chrome DevTools (F12) console?

hallj05

Yeah, I don't think it's the browsers the issue since it used to work in these browsers before.
 
I'm thinking that it has to be some change that was made elsewhere in the code (since this software is still in development). Since the reports used to work with no issues and then they just started to give this error, but I'm not sure how long it's been doing this so I can't compare all changes made recently to see what else could be causing this.
 
Yes, the error was showing in the Chrome DevTools, and it shows it happening in a file that is from Actuate (showing sample part of this below)
 
 * Contributors: 
* Actuate Corporation - initial API and implementation 
*******************************************************************************/ 
/** 
* This JavaScript library defines classes and methods to handle interactivity 
* actions on Chart, it is valid for SVG format. 
* 
* @since 2.5.1 
*/
 
 
We are using the BIRT Viewer Tag library and our page for it looks like below (which this hasn't changed since it was working)
 
<div class="Birt"> 
 
<birt:viewer id="${param.id}" reportDesign="${param.reportDesign}" pattern="frameset" format="html" scrolling="yes" height="${param.reportHeight}" width="${param.reportWidth}" showParameterPage="false"> 
 
<c:forEach items="${param}" var="par"> 
<c:if test="${par.key != 'reportDesign'}"> 
<birt:param name="${par.key}" value='${par.value}'></birt:param> 
</c:if> 
</c:forEach> 
</birt:viewer> 
</div>

Clement Wong

I'm not sure if I saw answers to my previous question... Are you able to test a simple report with SVG from the Designer using the same problematic browsers?
 
In regards to the HTML page with the BIRT tag library references, do you have a DOCTYPE declaration at the beginning. If so, what is it?

hallj05

Sorry for the delay in response. I didn't notice that you had responded.
 
We have discovered that the following jar seems to be causing the issue:Saxon-HE-9.4.jar
 
How do we make it so that the Birt graphs work with us having that jar? Since Saxon is used elsewhere in the app.

Clement Wong

I'm not sure about Saxon-HE-9.4.jar and how you are using it with BIRT.
 
BIRT 4.4.2 ships with org.eclipse.wst.xsl.saxon_1.0.200.v201103081755.jar.
 
So did you confirm that a simple report with a SVG chart from the Designer using the same problematic browsers works OK?

hallj05

The Saxon jar was getting used elsewhere in the application.
 
If I remove the jar then the reports would work again without issue.
 
The fix that we are using to make the reports work with the Saxon jar is we put the following where we defined all our BIRT params
 
 Properties props = System.getProperties(); 
 props.put("javax.xml.transform.TransformerFactory", "org.apache.xalan.xsltc.trax.TransformerFactoryImpl"); 
 System.setProperties(props);