When a new line is placed right after a nbsp, the new line is ignored in the layout. This can be reproduced by importing the following HTML:

First&nbsp;<br/>Second

Click event are not raised, and the command in the Command property is not executed, when a Button is placed inside InlineUIContainer, and is tapped on a touch device.

Workaround: One way to work around this is by setting TouchManager.TouchMode of the button to None, which will exclude the button from the TouchManager and will let the .NET events reach it. The other is to use the TouchManager Tap event instead of Command or Click.

Add support for Eastern Arabic Numerals in list level bullet text: https://en.wikipedia.org/wiki/Eastern_Arabic_numerals

Empty paragraphs are always exported with one empty span containing   When you apply styling like highlight color the span with   will be with background. Which is not the behavior in RTB.

An OutOfMemoryException is thrown on export to PDF when the compression mode is set to Deflate.


Regression, introduced in R1 2017.

Workaround: Change the ImagesCompressionMode to one of the other available options to avoid using the Deflate

Content Control Properties 'Use a style to format text typed into the empty control' option lost after XAML Export-Import

Insert a Plain Text Content Control to current document.

Enter a character in the Content Control.

Undo and then Redo.

The  Content Control remains in placeholder mode, which is not supposed to.

Current date in Date Picker Content Control cannot be selected.

ChangeFontHighlightColorCommand, ChangeParagraphBackgroundColorCommand, ChangeFontForeColorCommand and ChangeUnderlineColorCommand does not apply the color when invoked with string containing the name of the color as parameter, e.g. 'red'.

Available in LIB Version 2017.2.828.

In RichTextBox when IsTrackChangesEnabled = true, in a numbered list, after indenting and unindenting a line, the numbering of the list is incorrect.

There is no translation in the different languages.

Available in LIB Version 2017.2.828.

The ShowPlaceholder property of Content Control is not handled correctly when importing docx files.

The MoveToCurrentWordEnd will move to a character before the last position when called from the last position in a word and the word is surrounded by annotations.
The MoveToCurrentWordStart will move to the previous word when called from the first position in a word and the word is surrounded by annotations

The behavior is also unexpected for MoveToFirstPositionInParagraph, MoveToLastPositionInParagraph. 

Hi Team,
              I am sending one html body to outlook 2013 which contain bulletedlist, till my desktop app its bullets are looking ok. but after sending it to outlook new email body, there are too much space between bullet and inline text, please provide input, how can i handle it.
I think my bullets having different pattern which outlook 2013 doesn't support.
Do i need to add any other property background position : inside; something like.


Please find the attachments,
Thanks
Deepak

When word contains non-letters symbols at its start and/or end, it's always considered incorrect by the spell checker, even when it's present in the spell checking dictionary. The most common case is with abbreviations like "dr.", which should be invalid when are typed without the period ("dr"), but valid otherwise ("dr.")

Partial workaround: add the word without the punctuation to the dictionary. The problem is that the word without the punctuation will also be considered correct.

Currently, the document won't be imported due to an exception when decoding the base64 string image source. The expected behavior is the document to be imported and the image to be shown as a missing image.

Available in LIB Version 2017.2.731.

As shown in the attached video

When importing a DOCX file, the SdtType of  Rich Text Content Controls is not recognized correctly

If you start a selection from the end of a line and go back down (at least one line) and go back to the initial position and release the mouse button, then if you press any of the keyboard arrow keys you will see that the caret's new position is shifted with one line downwards. This is reproducible inside the R1 2023 QSF Examples. You can check the attached video for a demonstration.

Add support for associated character properties when importing from RTF. Such properties are 
\rtlch, \ltrch, and the associated control words like \afN, \loch, \hich, and \dbch.
Currently, runs/bullets with such properties set could be imported with different character properties.

Workaround: Use the supported \f tag for the most common low-ANSI characters, for example by:
- doing the following replaces in the source document:
\loch\af -> \loch\f
\dbch\f -> \dbch\af
- (Possible workaround) Re-saving the document with MS Word