PDF content editor limitations | Nutrient

This article documents known limitations and issues with the content editor in Nutrient Web SDK, along with recommended workarounds and version-specific fixes.

Mobile editing issues

The content editor has specific limitations when used on mobile devices.

View jumps to first page when activating text edit on iOS

When using the content editor on iOS devices (particularly in Chrome), tapping to edit text on pages beyond the first page may cause the view to unexpectedly scroll back to page 1. The keyboard may also fail to appear in some cases.

Affected versions — 1.8.0 and later

Platforms affected — iOS (Chrome, Safari)

Workaround — For documents requiring extensive text editing, use a desktop browser for the best experience. Mobile devices are better suited for viewing and light annotation tasks rather than heavy content editing.

Input method editor (IME) and composition input limitations

Input method editors and text composition systems may not work correctly with the content editor.

Cursor moves backward with Vietnamese IME (UniKey)

When typing Vietnamese text using the UniKey IME in VNI mode, the cursor jumps back one character each time a tone mark is applied. For example, typing D followed by 9 (which converts to Đ) results in the tone being applied correctly, but the cursor moves one position backward.

Affected versions — 1.8.0 and later

Platforms affected — Windows with UniKey IME

Workaround — Use the built-in operating system keyboard for Vietnamese input instead of third-party IME tools such as UniKey. The native Windows Vietnamese keyboard does not exhibit this issue.

This limitation specifically affects third-party IME software. Native operating system input methods work as expected.

Text annotation export issues

Exporting documents with text annotations can result in unexpected behavior.

Multiline text annotations truncated on export

When creating text annotations with multiple lines (using the Text tool and pressing Enter to create new lines), the content on the last line may be cut off or truncated when the document is exported or downloaded.

Affected versions — 1.8.0

Status — Fixed in version 1.9.1

Resolution — Upgrade to Nutrient Web SDK version 1.9.1 or later. The following fixes address this issue:

• Fixes multiline text annotations losing their custom size when editing. (1.9.1)
• Fixes text and callout annotations overflowing the document page when editing. (1.10.0)

Workaround for 1.8.0 — If upgrading isn’t immediately possible, try the following:

1. After creating multiline text, click outside the annotation to deselect it.
2. Reselect the annotation and manually resize the bounding box to ensure all text is visible.
3. Verify the content appears correctly before exporting.

Toolbar and UI limitations

Toolbar controls and UI elements may not display or function as expected.

Font size not displayed in action bar during text editing

When editing existing text in a PDF using the content editor, the font type may be displayed in the action bar, but the font size control may not appear.

Affected versions — 1.8.0 and later

Workaround — You can programmatically access and modify font properties using the content editing API. Refer to the content editing API documentation for details on working with text properties programmatically.

Version upgrade recommendations

If you’re experiencing issues with the content editor, consider upgrading to the latest version of Nutrient Web SDK. The following versions include significant content editor improvements.

Refer to the changelog for a complete list of fixes and improvements in each version.

Reporting issues

If you encounter content editor issues not listed here, report them through our support channels. When reporting, include:

1. SDK version number
2. Browser and version
3. Operating system and version
4. Steps to reproduce the issue
5. Expected vs. actual behavior
6. Any relevant console errors

For guidance on reporting bugs, see our bug reporting guide.