During the transition of various apps to be fit for 14.5 we very soon encountered a problem with the newly integrated TinyMCE editor which replaces the old CKEditor for richtext controls on Xpages.
To reproduce create a new XPage and paste this code:
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
<xp:div id="refresh">
<xp:inputRichText id="inputRichText1"></xp:inputRichText>
</xp:div>
<xp:div id="refresh2">
<xp:inputRichText id="inputRichText2"></xp:inputRichText>
</xp:div>
<xp:div>
<xp:button
value="PR RTF"
id="button1">
<xp:eventHandler
event="onclick"
submit="true"
refreshMode="partial"
refreshId="inputRichText1">
</xp:eventHandler>
</xp:button>
</xp:div>
<xp:div>
<xp:button
value="PR DIV"
id="button2">
<xp:eventHandler
event="onclick"
submit="true"
refreshMode="partial"
refreshId="refresh">
</xp:eventHandler>
</xp:button>
</xp:div>
</xp:view>
You can see 2 buttons, one of them refreshes the 1st control directly (which works perfectly fine using the old CKE) and the 2nd refreshes the container around the control. With TinyMCE on a Domino 14.5 you will see that refreshing the control destroys it where the partial refresh of the container does the trick here.
You can also see the 2nd control being destroyed everytime the 1st editor is being refreshed.
This means the following:
Domino 14.5 with the new richtext control breaks all apps that use more than one richtext field on a page and use partial refresh - which I assume are quite common. You may also check and consider re-designing your page(s) if you were used to refresh the richtext field directly. You now have to modify the refresh to use a container around the control.
A case is currently being processed, there is no KB article yet.