We previously had the problem that inner HTML in the tag was not allowed as string was expected. We seem to still have a similar issue with inner HTML in the item.html descriptions now.
Ideally, I want to use these descriptions for complext HTML embedding, including IIIF image viewers, to be displayed in a separate container underneath my location text box. However, it seems that here, too, string was the expected return. While this option should be possible, there should also be the possibility to work with full HTML embeddings.
The workflow I would like to see is this:
-
If correct combination is applied to a feature in a HTML location text, the engine checks what's in the related .html file for the item / feature and displays it as either text OR HTML in the bespoke container.
-
If the wrong combination is applied, either a default fail text is displayed (suitable for all combinations) OR a special alternative text from the item.ts or feature.ts file is shown in the same box where the combination buttons are (box on right-hand side of the screen).
-
When a combination is activated, the combination text label is shown in the combinations box on the right hand side of the screen.
-
When a valid combination is selected, the target name (item or feature name) is also displayed in the combinations box.
Challenges:
The handling of the feature description results are still inconsistent. It seems that several lines of code still expect strings by default, which does not correspond with my current samples. The flexibility to display both text strings and full HTML has to be ensured.
We previously had the problem that inner HTML in the tag was not allowed as string was expected. We seem to still have a similar issue with inner HTML in the item.html descriptions now.
Ideally, I want to use these descriptions for complext HTML embedding, including IIIF image viewers, to be displayed in a separate container underneath my location text box. However, it seems that here, too, string was the expected return. While this option should be possible, there should also be the possibility to work with full HTML embeddings.
The workflow I would like to see is this:
If correct combination is applied to a feature in a HTML location text, the engine checks what's in the related .html file for the item / feature and displays it as either text OR HTML in the bespoke container.
If the wrong combination is applied, either a default fail text is displayed (suitable for all combinations) OR a special alternative text from the item.ts or feature.ts file is shown in the same box where the combination buttons are (box on right-hand side of the screen).
When a combination is activated, the combination text label is shown in the combinations box on the right hand side of the screen.
When a valid combination is selected, the target name (item or feature name) is also displayed in the combinations box.
Challenges:
The handling of the feature description results are still inconsistent. It seems that several lines of code still expect strings by default, which does not correspond with my current samples. The flexibility to display both text strings and full HTML has to be ensured.