Note that LiveData Exporter should probably preferrably determine how the cell would be rendered by the LiveData Table, instead of blindly stripping whatever it thinks is HTML.
For example, a table could intentionally return HTML examples to be rendered as plain text as-is, in contrast to cells rendered server-side to be passed through to the browser without escaping.
Alternatively the other way around: Cell contents passed to the browser for rendering, which however don't "officially" start with an HTML tag, but can contain HTML entity references or embedded tags.
LiveData "knows" which cells are intended to be rendered as raw HTML, and the LiveData Exporter might somehow be able to use this information.
Gunter Ohrner on 27/Apr/26 13:34
Note that LiveData Exporter should probably preferrably determine how the cell would be rendered by the LiveData Table, instead of blindly stripping whatever it thinks is HTML.
For example, a table could intentionally return HTML examples to be rendered as plain text as-is, in contrast to cells rendered server-side to be passed through to the browser without escaping.
Alternatively the other way around: Cell contents passed to the browser for rendering, which however don't "officially" start with an HTML tag, but can contain HTML entity references or embedded tags.
TheLiveData table view "knows" which cells are intended to be rendered as raw HTML, and the LiveData Exporter might somehow be able to use this information.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
