TextualBody value is always rendered as html

[flamsens]

In the annotation panel, the value of a body of type TextualBody is always rendered as html, even if the body has a format set to text/plain.

The rendering should respect the mime type and only render the value as html if the MIME type is set to 'text/html'. Default is text/plain. The rendering should respecting line endings.

[marlo-longley]

Thank you for reporting this @flamsens
In this example from the IIIF cookbook, I see the text/plain annotation rendered inside a <span> element.
Can you provide more info on what you expect or want to be different? And provide a manifest that demonstrates your issue?

{
    "id": "https://iiif.io/api/cookbook/recipe/0266-full-canvas-annotation/canvas-1/annopage-2/anno-1",
    "type": "Annotation",
    "motivation": "commenting",
    "body": {
      "type": "TextualBody",
      "language": "de",
      "format": "text/plain",
      "value": "Göttinger Marktplatz mit Gänseliesel Brunnen"
}

[flamsens]

Hi @marlo-longley,

This IIIF cookbook recipe gives some guidelines on how to handle HTML in annotations:

• specify a format text/html
• wrap the value in a <span> or <p> tag (or start with a < and end with >)

Now consider this text example:

@tablet
@obverse
...
9. SAG.BI.<1(disz).KAM> {d}EN.ZU-i-sze?-na?-am? 
10. SAG.BI.<2(disz).KAM> ir3-ra-<ba>-ni 
11. SZA3.BA 3(u) SAR szi-ib-tum 
...

It is part of a transliteration of a cuneiform clay tablet, formatted in ATF format. The text contains HTML-like tags (<ba>) and HTML unsafe characters. It should never be rendered as HTML.

With a format set to text/plain, I would expect the viewer to

• encode HTML unsafe characters (< as <, > as >, & as &)
• respect line endings (using css white-space: pre-wrap)

With a format set to text/html, I would expect the viewer to

• filter unsafe HTML tags
• render the value as HTML