Xopus 5.2.2

This version fixes various bugs introduced in Xopus 5.2 and Xopus 5.2.1.

Release date: 2014-11-17

Release notes

  • Fixed a bug where setting a save function no longer worked

  • Fixed a bug in IE9 when inserting reference to a video: "DOM Exception: INVALID_CHARACTER_ERR (5)"

  • Fixed a problem in IE when using an xml file with inline configuration instead of using an Xopus island

  • Fixed a problem in IE when using Xopus without xsl defined for a view

  • Fixed a bug that Find/Replace was no longer working after loading a new document in Xopus

  • Fixed the problem in IE that Xopus scrolled to the top of the document when copying a selection

  • Fixed a problem that content copied before loading another document could not be pasted anymore

  • Fixed a bug in IE10 where Xopus crashed after cutting an image

  • Fixed a bug where javascript called from XSL did not work

  • Fixed a script error in EmbeddedXopus (embedded.js)

  • Fixed the bug that the XopusUnloaded event was not always fired

  • Fixed a problem that caused IE10 to error when using setViewParameter

  • Fixed a bug that multiple paragraphs could not be cut

  • Fixed a bug that the selection was incorrect after cut

  • Fixed problems with copy/paste from Word in IE9+

  • Fixed an error in IE9 when using XopusCanvas.enable after loading a new document

  • Fixed a problem that some characters are incorrectly seen as word separators by the spellchecker

  • Fixed a bug that custom buttons are not removed from the toolbar when another Xopus island is loaded

  • Fixed a bug where calling loadDocument did not completely unload the document

  • Fixed a bug where having two Xopus islands with the same document would result in errors

Known issues

  • Problems with rendering html content after the Xopus island in IE:

    In IE10 and later, html content after the <xml> island in the html might not be rendered correctly if self-closing tags are used in this xml. Wrap an extra <div> tag around <xml> or replace self-closing tags with pair-closing tags to resolve it.

  • Deleting table header cells when using the HTML table model:

    When using the HTML table model, the protection in Xopus that individual header cells cannot be removed is not working properly. When pressing delete or backspace in an empty header cell, the cell will be removed. This can result in a table that, although schema-valid, is not a correct structure.

    A workaround to prevent this problem is to assign the "tablecell" role as well to the "th" element in configuration:

    <x:node match="th">
      <x:role>tableheadercell</x:role>
      <x:role>tablecell</x:role>
    </x:node>
  • Possible broken table structure when using the HTML table model:

    When using the HTML table model, the protection in Xopus that individual cells cannot be removed is not working properly. When deleting a selection that spans over multiple cells, cell elements can be removed. This can result in a table that, although schema-valid, is not a correct structure.

Anonymous