Known issues

Due to technical limitations, Fonto Editor is not compatible with browser extensions that modify the page, especially ones that do so to support editing. Using such extensions with Fonto Editor may cause unexpected behavior, including poor performance, sudden selection changes, being unable to move the cursor and/or unexpected changes being made in your documents. If you encounter such issues, please check your browser's configuration and try disabling any extensions (or add-ons in Firefox) that may be interfering.

We are currently aware of the following extensions causing problems when working in Fonto Editor:

• Google Input Tools

• Avaya

If you encounter other extensions that interfere with the editor or any other Fonto product, or if you are the author of an extension that is not compatible, please let us know. We always try to reach out to and work together with the extension authors to resolve compatibility issues.

We are aware of a known issue in Fonto 7.12.0 where the deprecation warning for createAttributeLabelWidget is thrown from the platform code of Fonto.

If you see the message "createAttributeLabelWidget is deprecated and will be removed in 7.14. Please use the createLabelQueryWidget instead. See https://documentation.fontoxml.com/editor/latest/upcoming-deprecations-7-14-33444398.html for more information.", perform a manual search through your editor for "createAttributeLabelWidget" and replace occurrences as described in the deprecation instructions.

Moving cursor while typing will result in misplaced content

Moving the cursor using the mouse while keeping a single character key pressed or while typing will result in misplaced content. Content may end up in the element that was first selected.

Find and replace currently operates in (XML) document order instead of visual order. This affects elements such as footnotes.

To always scroll the correct result into view keep the search running, use scoped search if a full search of all documents takes too long.

When using XQUF to create an element in a namespace, the prefix will be used to serialize new elements to JSONML. If the prefix is not registered in the NamespaceManager, this will cause the wrong namespace to be used. To circumvent this, use the namespace prefixes that are registered in the NamespaceManager.

For example, when a selection starts within bold text, ends outside that bold text and italic formatting is applied, only the non-bold part of the selected text will be italic.

Nested list items can exceed the sheetframe border after a large number of nesting. You can avoid this by limiting the amount of sublists via the configureAsInvalid function. For example by using: configureAsInvalid(sxModule, 'self::ol/count(ancestor::ol) > 6');

This might result in one of the following errors:

• Error: XQST0051: No modules found with the namespace uri ...

• Function ... with arity of ... not registered.(This error can also be caused by other coding issues)

This is caused by the Editor startup order, which processes the XQuery Modules *.xqm files before the code (per package). In order to work around this issue, move the code to a separate package and add a dependency to the new package it in the existing package.

This is caused by the way positions currently work in Fonto. Positions won't get lost, but just get expanded. Workaround is to use the created context modal to see the original image the comment was placed on.

Applicable in all supported browsers and all operative systems. This is more common on Windows machines that have a 125% display scale by default.

This is caused by the way we currently create cursor positions for the browser. Screenshots below illustrate the issue.

Without the formatting:

With the formatting:

This is due to the spec allowing browsers to ignore justification when whitespace should not be collapsed, which we use in Fonto. This is noticable in tables that have this setting.

Using iframes inside views is highly discouraged as iframes frequently re-render every time the view updates. This can be expensive and may affect performance. There are also known browser issues with using iframes inside views.