Hi Mike!
I had a quick question
We have some old reports and since upgrading to Prince9, we've noticing a lot of our reports were having rendering issues. Upon further investigation, it seemed that things in our xsl previously like this
<div class="certificateLogo" />
[self closing div.]
that was styled like this:
.certificateLogo {
margin:0;
padding: 0;
height: .5in;
background-image:url("/images/LogoCert.svg");
background-repeat: no-repeat;
background-position: center;
}
the div was now being rendered through Prince as <div class="certificateLogo"> and acting as a parent to all subsequent divs, instead of a sibling.
another example was in the xsl, when an if statement was not
<p>
<b><xsl:value-of select="/session/page/blah/blah[@type='position']/."/></b>
</p>
<p>
<b> ...
and the <b> wraps the remainder of the document.
Has anyone else encountered this change in rendering behavior since moving prince versions?
Thanks!
I had a quick question
We have some old reports and since upgrading to Prince9, we've noticing a lot of our reports were having rendering issues. Upon further investigation, it seemed that things in our xsl previously like this
<div class="certificateLogo" />
[self closing div.]
that was styled like this:
.certificateLogo {
margin:0;
padding: 0;
height: .5in;
background-image:url("/images/LogoCert.svg");
background-repeat: no-repeat;
background-position: center;
}
the div was now being rendered through Prince as <div class="certificateLogo"> and acting as a parent to all subsequent divs, instead of a sibling.
another example was in the xsl, when an if statement was not
<p>
<b><xsl:value-of select="/session/page/blah/blah[@type='position']/."/></b>
</p>
<p>
<b> ...
and the <b> wraps the remainder of the document.
Has anyone else encountered this change in rendering behavior since moving prince versions?
Thanks!