We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement suggestion.
Currently, content search only renders plain text, see
clover-iiif/src/components/Viewer/InformationPanel/ContentSearch/Item.tsx
Line 114 in 69c6cf2
Elsewhere in the codebase, you check the body type and use the appropriate component (plain / HTML / VTT / image):
clover-iiif/src/components/Viewer/InformationPanel/Annotation/Item.tsx
Line 51 in 69c6cf2
The use case here is for enhancing search results, for example, with: Text surrounding <mark>your search term</mark> example
Text surrounding <mark>your search term</mark> example
However, you may want to sanitise this (perhaps your existing AnnotationItemHTML component does this already?) as I can imagine plenty of markup here that could break things. We do a similar thing on Storiiies viewer: https://github.com/CogappLabs/StoriiiesViewer/blob/5da2e2a7d3b020f63b789bcb3328f8d0dad1c8ed/src/StoriiiesViewer.ts#L145
AnnotationItemHTML
The text was updated successfully, but these errors were encountered:
mathewjordan
No branches or pull requests
Enhancement suggestion.
Currently, content search only renders plain text, see
clover-iiif/src/components/Viewer/InformationPanel/ContentSearch/Item.tsx
Line 114 in 69c6cf2
Elsewhere in the codebase, you check the body type and use the appropriate component (plain / HTML / VTT / image):
clover-iiif/src/components/Viewer/InformationPanel/Annotation/Item.tsx
Line 51 in 69c6cf2
The use case here is for enhancing search results, for example, with:
Text surrounding <mark>your search term</mark> example
However, you may want to sanitise this (perhaps your existing
AnnotationItemHTML
component does this already?) as I can imagine plenty of markup here that could break things. We do a similar thing on Storiiies viewer:https://github.com/CogappLabs/StoriiiesViewer/blob/5da2e2a7d3b020f63b789bcb3328f8d0dad1c8ed/src/StoriiiesViewer.ts#L145
The text was updated successfully, but these errors were encountered: