--- title: "2019.2 release notes" canonical_url: "https://www.nutrient.io/guides/web/release-notes/2019-2/" md_url: "https://www.nutrient.io/guides/web/release-notes/2019-2.md" last_updated: "2026-08-13T07:22:52.665Z" description: "Learn about the API changes and migration steps for PSPDFKit for Web 2019.2, including updates to annotation, bookmark, and form field methods." --- [PSPDFKit for Web 2019.2](https://www.nutrient.io/blog/pspdfkit-web-2019-2/) comes with a few improvements that might require an ad hoc migration. ### Notable changes - We renamed all `*.onPress` events to `*.press` to improve consistency with our event naming schema. The old names are now deprecated and will be removed in a future version. The name changes are as follows: - `annotations.onPress` to `annotations.press` - `textLine.onPress` to `textLine.press` - `page.onPress` to `page.press` - Shape annotations had their stroke width scaled when resized with the UI. As a result, the different annotations’ stroke widths could vary if resized. This behavior has been changed, so now a shape annotations’ stroke width is kept when resizing. - The default minimum stamp annotation size, `NutrientViewer.Options.MIN_STAMP_ANNOTATION_SIZE`, has been increased from `10` to `15`. The former value was so small that stamp annotations resized that small would have their text clipped in a way that the stamp text wouldn’t fit (#2977). If your code relies on the former value, you can set it before the first `NutrientViewer.load()` call: `NutrientViewer.Options.MIN_STAMP_ANNOTATION_SIZE = 15`. - In a recent version, we accidentally disabled an optimization that reduces the number of points an ink annotation creates while drawing. This release restores the previous behavior. You can opt out this behavior by setting `NutrientViewer.Options.INK_EPSILON_RANGE_OPTIMIZATION = 0`. - We renamed `FormField#annotationPdfObjectIds` to `FormField#annotationIds`. - When in continuous scroll mode, we now remove custom overlay items from the DOM if you scroll a certain number of pages below the page they items are rendered on. If you previously depended on custom overlay items being persisted in the DOM (e.g. wanted to maintain its state), you will now have to handle this explicitly with the `CustomOverlayItem#onDisappear` method. For example, if you’re using a `