ID 232187 - HTML input not displayed correctly when read as an expression

Problem summary
Using some HTML in a text knob and sourcing this as an expressioned value within a Text node will display the text in the Viewer incorrectly, with visual artefacts.

Customer reported version
nuke.10.0v3

Customer reported platform
windows7

Steps to reproduce

1) open attached example script
2) the Group node contains 2 text input knobs, one with plain text and one with HTML characters/codes. Sourcing their values via TCL or Python commands as expressions within a Text node, is displaying the HTML input incorrectly as follows:

This is similar when the text input is sourced from a Group node knob or from within a message box in another Text node.

Workaround
Unknown.

Reproduced by support

Reproduced in Nuke 9.0v8 and Nuke 10.0v3. In Nuke 8.0v6 the visual artefacts don't appear but the HTML code is processed at all and is shown as plain text.

HTML should be interpreted and display correctly when sourced via an expression from a different node.

Actual behaviour
HTML previewing seems to introduce artefacts when value is retrieved via TCL/Python expressions from another node.