Adding comments and replies in JavaScript PDF viewer

Nutrient Web SDK provides a user interface (UI) for viewing, adding, and deleting comments in PDF documents. Comments enable collaborative workflows where multiple users can discuss specific sections of a PDF document without leaving the viewer.

If you’re using Nutrient Web SDK with Document Engine and have Nutrient Instant enabled, comments are available starting from version 2020.1. For more information, refer to the Nutrient Instant guide.

If you’re not using Document Engine, comments are available starting from version 2023.3.

The main difference between the two setups is how collaboration works. With Document Engine, users see each other’s changes in real time. Without it, collaboration is asynchronous — changes appear only after a document is reloaded.

Licensing

Comments require a separate component in your Nutrient license. Without this included in your license, you won’t be able to add the functionality of viewing, searching, or adding comments in your application. Contact our Sales team to add comments to your license.

If you’re a new customer, you can try comments without a license key. If you’re an existing customer, ask our Sales team for a trial license if you’re interested.

Terminology

Before starting, here are a few key terms related to comments:

Root annotation — The annotation to which all the comments in a single thread are linked.
Comment thread — A group of comments associated with the same root annotation.
Comment — A single comment added by a user.

Root annotation types

All comments are linked to their respective root annotations. The comments with the same root annotation are part of a single comment thread. There can be two types of root annotations:

MarkupAnnotation — You can start a new comment thread by selecting some text and clicking in the markup annotation inline toolbar. In this case, the markup annotation created will act as a root annotation.
CommentMarkerAnnotation — A comment marker annotation is a new annotation that can be added anywhere in a PDF document and used to start comment threads.

Getting started

By default, we don’t show the comment tool () in the main toolbar. This is because we want you to think about the workflow you want for your users and then decide whether or not you want to add it in the main toolbar. For example, if you want to enable the creation of comments from the main toolbar and disable sticky notes, use the following code snippet:

const toolbarItems = PSPDFKit.defaultToolbarItems
    .concat({ type: 'comment' }) // Add comment tool.
    .filter((item) => item.type !== 'note'); // Remove note tool.

PSPDFKit.load({
    // ...
    toolbarItems,
});

You’ll have to add the comment tool in the main toolbar if you want to add comments using the comment marker annotation.

Adding a comment

You can add comments in two ways, depending on the type of root annotation.

This method involves the creation of CommentMarkerAnnotation before the creation of comments. To add a comment marker annotation, click the comment tool () in the main toolbar and choose a location on the page where you want to add the comment. A comment editor will appear where you can write your first comment and start a new thread.

Comment main toolbar

Using markup annotations

To add a comment linked to a text annotation, create a new markup annotation and click the comment tool () in the inline toolbar. This opens a comment editor where you can write your first comment and begin a new thread.

Comment inline toolbar

Mentioning users in a comment

To mention a user in a comment, type @, followed by the user’s name, and select the user from the list.

Setting the list of mentionable users

To specify the users who can be mentioned in comments, follow the steps below.

Create a MentionableUser object for each mentionable user with the following string type properties:
- Required: name, id, displayName
- Recommended: description
- Optional: avatar
Create a list of the MentionableUser objects.
Pass the list to the mentionableUsers configuration property when you load the Nutrient Web SDK viewer, or to the setMentionableUsers method after loading the viewer.

The example below sets two mentionable users when loading the Nutrient Web SDK viewer:

PSPDFKit.load({
    // ... Other configuration options.
    mentionableUsers: [{
            name: "Jane Doe",
            displayName: "Jane Doe",
            id: "jane_doe",
            description: "[email protected]"
        },
        {
            name: "John Doe",
            displayName: "John Doe",
            id: "john_doe",
            description: "[email protected]"
        }]
})

The example below changes the list of mentionable users after the Nutrient Web SDK viewer has loaded:

instance.setMentionableUsers([{
        name: "Jane Doe",
        displayName: "Jane Doe",
        id: "jane_doe",
        description: "[email protected]"
    },
    {
        name: "John Doe",
        displayName: "John Doe",
        id: "john_doe",
        description: "[email protected]"
    }])

Getting the list of users mentioned in a comment

To get the list of all users mentioned in a comment, call the getMentionedUserIds method on the comment object:

comment.getMentionedUserIds()

Notifying mentioned users

To notify users who are mentioned in a comment, add event listeners to the loaded instance.

One approach is to listen to the changes made by a specific user. To do this, listen to the comments.mention event and send notifications when the event is triggered. In the example below, the listener is triggered when the user john_doe adds or removes the someCommentObject comment. The listener won’t trigger if the changes are made by another user, even if those changes are visible to you:

instance.addEventListener("comments.mention", args: {
    comment: someCommentObject,
    modifications: [{
        userId: "john_doe",
        action: "ADDED" | "REMOVED"
        }]
    } => void)

Another approach is to listen to all changes to comments irrespective of who made them. Listen to the comments.create, comments.update, and comments.delete events to send notifications when comments are created, updated, or deleted. The example below adds separate event listeners for each of these three cases and determines the users mentioned in the affected comments. If you implement a way to keep track of users mentioned in different comments, you can determine if new user mentions have been added or deleted and send notifications to the affected users. This approach gives you control over the different ways comments can change (creation, update, deletion). The limitation of this approach is that changes by any user will trigger notifications; you cannot specify the users whose changes will trigger notifications. Using this approach, you can’t determine who made the last change to a comment, but you can use the comment.creatorName property to determine the user who created the comment:

instance.addEventListener("comments.create", createdComments => {
    const users = createdComments
        .get(0)
        .forEach(comment => comment.getMentionedUserIds())
})

instance.addEventListener("comments.update", updatedComments => {
    const users = updatedComments
        .get(0)
        .forEach(comment => comment.getMentionedUserIds())
})

instance.addEventListener("comments.delete", deletedComments => {
    const users = deletedComments
        .get(0)
        .forEach(comment => comment.getMentionedUserIds())
})

Deleting a comment

You can delete an individual comment by clicking the () delete button. If all the comments of a thread are deleted, the corresponding root annotation is automatically deleted.

Document Engine currently doesn’t expose any APIs for deleting a comment.

Disabling the comments UI

If your license includes comments but you want to disable letting the user view and add comments, you can set showComments to false in ViewState:

const initialViewState = new PSPDFKit.ViewState({
    showComments: false,
});

const instance = PSPDFKit.load({
    // ... other options
    initialViewState: initialViewState,
});

Comment permissions

There might be situations where you want to disable the creation or deletion of individual comments based on some condition. To do this, you can define the isEditableComment function as a configuration option when initializing the viewer. When the return value of the isEditableComment method is false for a comment, the comment can no longer be deleted by the user. Similarly, isEditableComment can be used to determine whether or not a user can reply to existing threads.

In the example below, all the comments that have a root annotation with an id other than the rootAnnotationId will be editable:

PSPDFKit.load({
    // ...
    isEditableComment: (comment) => {
        return comment.rootId !== rootAnnotationId;
    },
});

For every comment thread, isEditableComment receives a temporary draft comment with pageIndex=null. The rootId of this draft comment points to the root annotation of the comment thread. If isEditableComment returns false, the user won’t be able to add comments in that comment thread.

In the example below, a user can’t add a comment in any comment thread:

PSPDFKit.load({
    // ...
    isEditableComment: (comment) => {
        return comment.pageIndex !== null;
    },
});

To set the permissions after a viewer instance has been created, you can use instance.setIsEditableComment:

PSPDFKit.load(options).then((instance) => {
    instance.setIsEditableComment((comment) => {
        return comment.rootId !== rootAnnotationId;
    });
});

Customizing a comment block

Customize the look of a comment block using CSS. Make sure you’re using the public class names starting with PSPDFKit-, as other class names might change in the future and break your application.

For example, if you want to customize the border-radius of avatars, you can do that by writing the following CSS:

.PSPDFKit-Comment-Avatar {
    border-radius: 6px;
}

You can also show avatars in comment blocks by setting a custom renderer:

PSPDFKit.load({
    customRenderers: {
        CommentAvatar: (comment: Comment) => ({
            node: element,
            append: false, // This should always be `false` in this case.
        }),
    },
});

If you want to change the avatar after the viewer instance has been created, you can use setCustomRenderers.

Responsive UI

The UI adapts to the screen size of your browser. In the case of large screens, comment threads are displayed in a sidebar on the right-hand side of a document and are always visible, while on smaller screens, the threads are only visible after you click/tap on a root annotation.

Rich text comments

Rich text editing is supported in comments. Using the UI, you can select parts of a comment and do the following:

Make parts of the comment bold, italic, or underlined.
Change the color and the background color of the parts of the comment.
Add hyperlinks to the comment.