Version 1.2 (06 May 2019)
This update improves how Acrolinx highlights issues in your content, and changes how Acrolinx recognizes browser extensions.
Improved Highlighting and Scrolling
Sometimes, Acrolinx accurately highlighted an issue but it wasn't visible on the page. We've improved how Acrolinx scrolls your content, so the highlighted issue is closer to the center of the page.
Highlighting in Tables in the Quip Editor
If you use Quip, you might have noticed that Acrolinx couldn't highlight issues in tables. We've improved Acrolinx to work reliably in Quip.
Note that sometimes you have to click a Sidebar card twice for Acrolinx to scroll to an issue in a table.
Consistent Highlighting in Salesforce Lightning Experience
Acrolinx wasn't very consistent with highlighting issues in Salesforce Lightning Experience. Sometimes it would accidentally highlight entire paragraphs, other times it wouldn't highlight issues at all. We've improved the highlighting and scrolling precision in Salesforce Lightning Experience.
Each Browser Extension Now Uses Its Own Signature
Until now, all browser extensions used the same signature to identify themselves to the Acrolinx Platform. We've now introduced unique signatures for each browser extension.
This change in signature means that the integration names used in Analytics will change. Acrolinx Analytics used to group all checks by browser extensions under the integration name "Browser Extensions". Now, Acrolinx Analytics shows you whether a check was made in Chrome, Firefox, Safari, or Microsoft Edge. The "Browser Extensions" group doesn't exist anymore.
This change also means you'll need an updated license to continue to use Acrolinx for Safari.
Update Your License
Now that each browser extension has a unique signature, you'll need an updated license to continue to use Acrolinx for Safari.
Update Your Custom Content Profiles
Did you use the default browser Content Profile as a template to create a customized Content Profile? If so, you'll need to update this customized Content Profile. The default browser Content Profile used to use the signature, which has now changed. We recommend not using the signature at all in these Content Profiles. Instead, you could use the public ID, system ID, and root element.
We've developed and tested this version of Acrolinx for Safari with Safari versions 11.0 and 11.1.
Acrolinx for Safari requires the following:
- Acrolinx version 5.2 or later