Version 1.7.9

Maintenance release + adds zh locale

Version 1.7.8

UI/ Behaviour

• Text entry fields in the editor now block the Delete key-up event, so that the annotation doesn't get deleted while the user edits text
• Comment widget now supports a disableReply property that will hide the reply field, if there is already a comment (#113)
• Comment and tag widget now support a placeholder property for overriding the text input placeholder text. This is an additional shortcut over the messages init property

Version 1.7.7

Bugfixes

• Fixes a bug that cause the TagWidget to fire a change event on initial render

Behavior

• When using Recogito to annotate content inside an iframe, the Editor auto-position now respects the iframe dimensions

Version 1.7.6

API

• Added onChanged callback function to Editor

Version 1.7.5

API

• Added hasChanges method to Editor, enabling host app to check if the user has changed the annotation state

Version 1.7.4

• Added Japanese UI translation (#108)
• Added Chinese UI translations (#106)
• Widgets can now add additional namespaces to the annotation @context.

Version 1.7.3

Bugfixes

Fixed a minor issue in the Selection class that caused error when accessing the exact field on image annotations. The call now returns null.

Version 1.7.2

Bugfixes

• Fixed a style regression bug that prevented line breaks is read-only comments
• Fixed a minor issue in the WebAnnotation class that caused error when calling exact, start and end on image annotations. These methods now return null

Version 1.7.1

• Line breaks in comments are now properly displayed in read-only mode (#100)
• The default editor width is now reduced responsively on small-screen devices (#101)

Version 1.7.0

Behavior/feature additions

• Added Russian UI translation
• Breaking change: tag bodies are now serialized differently when terms are from a semantic vocabulary (label + URI) (#94):

{
  "type": "SpecificResource",
  "purpose": "tagging",
  "source": {
    "id": "http://vocab.getty.edu/aat/300010358",
    "label": "material"
  }
}

Non-semantic terms are still represented in the same way, as a TextualBody with a value:

{
  "type": "TextualBody",
  "value": "material",
  "purpose": "tagging",
  "source": "http://vocab.getty.edu/aat/300010358"
}