FontoXML 6.3.0 (May 13, 2016)

Resolved issues

  1. The cursor no longer jumps to the start of the document when right-clicking an image.
  2. Changing the xml:lang attribute now correctly updates spelling suggestions.
  3. References that can not be resolved can now be deleted correctly.
  4. Continued typing before a lock request fails no longer causes many errors to appear in the browser console.
  5. In some cases, find and replace could skip results in documents that were not scrolled into view. This has been resolved.
  6. Editing a comment no longer results in the error page being shown.
  7. If uploading an asset failed, selecting the same asset file again now correctly retries the upload in Chrome.
  8. Using the XPath “or” operator with selectors targeting different element names no longer throws an error.
  9. Selecting the last card in the review panel now correctly scrolls the card’s buttons into view.
  10. Editing a comment shown as the last card in the review panel now correctly scrolls the updated card into view.
  11. Various internal stability improvements.

New functionality

  1. A new IndexManager API has been added for extension developers to efficiently access and track all nodes matching a selector.
  2. Support has been added for the XPath true() and false() functions.
  3. If documents fail to load correctly, Fonto now shows a placeholder instead of going to the error page. The error page is only shown if all top-level documents fail to load. Please refer to the browser’s developer console for more details on the nature of these errors.
  4. Fonto now supports pasting tables from external sources. Please refer to the developer documentation and the DITA example configuration in fontoxml-dita-sx-pivot-model-translation for details on how to configure this for your Schemas.
  5. Fonto now uses Angular 1.5.5. See https://github.com/angular/angular.js/blob/master/CHANGELOG.md for an overview of changes in this version.
  6. Fonto now exposes the type of error to the error page in cases where it is known. Custom error page templates can use the {{errorRoute.category}} value to customize the displayed content for specific cases. Current categories are “operation-failed”, “document-save-failed” and “initial-document-load-failed”.
  7. CMS errors encountered by the standard browse modals now result in an error message instead of "no documents" or "no images". This template can be configured by setting stateMessageErrorTemplateId in the operation opening the modal. Applications using custom browse modals should make sure to set the state-message-error-template-url attribute on the ui-asset-browser element.
  8. Fonto now shows a configurable warning modal instead of the error route if an operation fails unexpectedly. Set the enable-experiment/use-operation-error-modal configuration value to false to return to the old behavior of redirecting to the error page, or mark specific operations known to be unrecoverable with the errorsAreFatal property. The contents of the warning modal can be customized by setting the operation-error-modal-content-template configuration value to a template url. To aid in debugging errors, Fonto now logs more detailed information to the developer console when operations fail to execute or determine their state.
  9. The Fonto development server and build tools now allow a packages-shared directory to be used in applications. This way, application developers can keep packages shared between applications separate from those specific to the application.
  10. The asset browser operations now pass the selected asset’s metadata in the resulting targetSpec property of the operation’s step data.

Other improvements

  1. Fonto now uses the most recent version of the node-sass library. Note that this version is more strict and may detect errors in your .scss files that were previously ignored.
  2. The standard browse modals now indicate errors encountered during upload by temporarily turning the button red.
  3. The standard taxonomy browse modal now indicates if errors are returned from the CMS during search.
  4. Clicking the previous and next result buttons in the find and replace form now places the cursor back in the find field. Likewise, clicking the replace and replace all buttons now places the cursor back in the replace field.
  5. Pressing Ctrl+H while the find & replace form is open now jumps to the replace field instead of opening the browser's history.