Maintain CSS classes/appearance from Jira JEditor
We use Jira (7.1.7) with JEditor (2.3.7) which gives us rich text capabilities in the Jira text fields.
We use Confluence (5.9.7) with Scroll PDF exporter (3.5.0).
Our common use case is to use the Jira macro in Confluence to get details of Jira issues into a Confluence document. We then export that document into PDF.
We have found an interesting limitation - we are making increasing use of styles provided by JEditor. These styles do find their way into Confluence correctly (we see the class name and the style information when the relevant elements are inspected) so in both Jira and Confluence upon inspecting the relevant element we see, for example:
<div class="jePanel_info" style="background-color:#E0EFFF;border-radius:.3em;border:1px solid #9EB6D4;padding:.5em 1em .5em 2.5em;">
However, although the above does appear in Confluence, it's not carried over into the export.
The relevant .xhtml files don't have anything in place of the div above.
Is there anything we can do about this?
Thanks for reaching out. Unfortunately the described behavior is a known limitation of our current Scroll PDF Exporter infrastructure, as divs and spans are not supported with the current version.
This limitation is tracked in our JIRA system: https://k15t.jira.com/browse/EXP-326 (looks like you're already watching the issue).
As you might know we're currently working on moving our Scroll PDF Exporter to a new library and also make some major changes in the overall architecture.
Until this change has happened (we currently plan to release this in Q3 2017), this issue won't be fixed. With the new version planned for Q3 we'll be supporting div and span elements in Scroll PDF Exporters.
So those changes will still need some more time (no specific ETA), so for now you'd need to live with this limitation.
If there's any workaround we'll communicate it as a comment at the mentioned issue, but we do not expect to have anything in place before the actual Scroll PDF Exporter 4.0 release in Q3.
Thanks for your patience and sorry for the inconveniences. If there's any more feedback, please let us know.
Please sign in to leave a comment.