We can look at wysiwyg later, but we could also detect and validate HTML in fields.
We can also detect when a user seems to be entering HTML but hasn't started and/or ended the string with a < (and '>'). For example, the string contains tags, but doesn't open with a tag.
If we can convey that the field has HTML (a subtle visual clue) we can then validate it (a vault validator helper?) as per the spec - only permitted tags. And offer a wysiwyg button/switch later.
Most free string fields (label, metadata pairs, summary etc) can take HTML as well as plain strings.
https://iiif.io/api/presentation/3.0/#45-html-markup-in-property-values
We can look at wysiwyg later, but we could also detect and validate HTML in fields. We can also detect when a user seems to be entering HTML but hasn't started and/or ended the string with a
<
(and '>'). For example, the string contains tags, but doesn't open with a tag.If we can convey that the field has HTML (a subtle visual clue) we can then validate it (a vault validator helper?) as per the spec - only permitted tags. And offer a wysiwyg button/switch later.