If you copy content from a Google Doc which contains italic and bold and paste it into a JCE instance, the italic and bold will be stripped out. This happens even if you have configured JCE to preserve all styles. The font-family and font-size are correctly preserved.
You can test this by copying the sentence from the following document into JCE:
The bug stems from the code that strips out font-style: normal and font-weight: normal. That code currently calls return even if you have font-style: italic or font-weight: 800. As a result this line after the switch statement is skipped,
outputStyles[name] = value;
And, accordingly, the font-style and font-weight tags are not included in the outputStyles, which means that the code which later rewrites the HTML to use <i> and <b> is never invoked.
The proposed fix only calls return when value == "normal". In other cases it merely calls break.
I have not completely tested this patch. I did test that removing the case "font-style": entirely fixes the problem, so I believe this patch should work as well.
If you copy content from a Google Doc which contains italic and bold and paste it into a JCE instance, the italic and bold will be stripped out. This happens even if you have configured JCE to preserve all styles. The
font-familyandfont-sizeare correctly preserved.You can test this by copying the sentence from the following document into JCE:
https://docs.google.com/document/d/1cyWjzFPIDZVYD7uZjObx_CcwRDmXtxtSCL3mShwUsF8/edit?usp=sharing
The bug stems from the code that strips out
font-style: normalandfont-weight: normal. That code currently callsreturneven if you havefont-style: italicorfont-weight: 800. As a result this line after theswitchstatement is skipped,And, accordingly, the
font-styleandfont-weighttags are not included in theoutputStyles, which means that the code which later rewrites the HTML to use<i>and<b>is never invoked.The proposed fix only calls
returnwhenvalue == "normal". In other cases it merely callsbreak.I have not completely tested this patch. I did test that removing the
case "font-style":entirely fixes the problem, so I believe this patch should work as well.