Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.3.0.GA_P03
-
Fix Version/s: EE-4.3.0.GA_P04, EE-3.3.0.GA_P10
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Support Case References:Support Case 14703 - https://icesoft.my.salesforce.com/5004u00002iAdR3
Description
When trying to use ace:printer to print an ace:richTextEntry component, only a blank page appears in the print preview window of the browser. It is well known that the CKEditor, upon which ace:richTextEntry is based, is a complex piece of javascript and that it uses an iframe for the editor's contents, which could be the reason why ace:printer is not working with it, as its approach consists in cloning elements into its own staging iframe for printing. This JIRA is to find an alternative approach for the ace:printer component to support printing the ace:richTextEntry component.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Added code to handle the special case of printing ace:richTextEntry components and also added related documentation.
At revision 53459 to the 4.x trunk.
At revision 53460 to the 3.x trunk.
At revision 53461 to the customer's branch.
The fix consists in rendering directly the javascript code necessary to directly print the ace:richTextEditor contents, without using the jqprint widget.