v1.2.3

Patch Changes

• Add polyfill for structuredClone

v1.2.2

Bugfix

Replaced AbortSignal.timeout with AbortController.abort, as it isn't supported on iOS 15

v1.2.1

• Fixes an issue where the wasm module would report the invalid SDK version
• Fixed URLs in the readme, documented createCaptureUiWithInstance

v1.2.0

1.2.0

• Added configuration options for tilt, blur and glare tolerance.

  These can be configured using the new AnalyzerSettings properties:

  • tiltPolicy
  • blurPolicy
  • glarePolicy

  Each value can have a StrictnessLevel:

  • "disabled"
  • "strict"
  • "normal" (default value)
  • "relaxed"

  The tiltThreshold, ignoreGlare, and ignoreBlur settings have been replaced with the new policies.

• Added keepDpiOnTransformedDocumentImage configuration on AnalyzerSettings which determines whether to preserve the captured document DPI in transformed document image. If disabled, the document DPI is downscaled to 400 DPI.

• The createCaptureUi function will now throw an error if there was an issue during the creation of the SDK.

• When booting up the SDK, the fetch function will time out after 3 seconds if it can't find the necessary resources.

• Added hasPing property to LicenseUnlockResult

• Added destroyInstanceOnDismount property on uiSettings which controls if the SDK instance, including the workers should be unloaded when the component is dismounted.

  This property is true by default when the ui is created using the createCaptureUi function and false when using createCaptureUiWithInstance.

• When using the headless API (createCaptureSdk), disconnecting the video element from the DOM will no longer destroy the SDK instance.

• Fixed a bug where the camera selector dropdown wouldn't be correctly displayed due to a missing z-index.

• Add fallback logic for generating user ID when local storage is blocked.

• Upgraded types for the localization strings. Will now show the original value in autocomplete.

• ExposedComponentApi has been deprecated and merged with CaptureComponent

• Improved error handling — createCaptureUi will now throw an error instead of silently failing during initialization.

v1.1.1

Patch Changes

• Removed the use of data: protocols when loading cross-origin workers. Will only use the blob: to be more flexible with different CSPs.

v1.1.0

New usage mode — Direct API

• Users can now initialize the SDK in a low-level DirectAPI mode using createDirectApi
• This mode gives users the capability to directly interact with the Analyzer instance, bypassing the provided functionality in the Capture SDK such as camera and video management, user feedback, callbacks and state management.

Capture SDK

New features:

Orientation check

• Added camera-orientation-unsuitable to DocumentFramingStatus. This status is returned if it's not possible to capture the document in its current orientation.
• When using the SDK the user will be guided to rotate the document.

Automatic DPI adjustment

• Added adjustMinimumDocumentDpi setting on the Analyzer. When enabled, the minimum dpi is adjusted to optimal value for the
  provided input resolution to enable capture of all document groups.

Camera stream mirroring

• Added the capability to mirror the camera stream horizontally. Enabled by default on front facing cameras.

• The current state can be found on the mirrorX property in the store and toggled using the setMirrorX method on the SDK instance.

Early finishing of side capture

• The finishSideCapture method has been added to the SDK instance which allows users to manually finish the capturing process early if there are any candidates available.

Breaking changes:

• The completenessStatus property on the AnalyzerResult spelling has been fixed (was completnessStatus)
• The frame and frameResult parameters in onFrameCallback have been swapped as the actual ImageData is required less often

Other changes:

• Improved guide for hosting resources
• CaptureSdk and CaptureUi provide a stricter API contract
• Lowered bundle size
• Improved error handling in the web worker
• videoFrameCallback is now only polyfilled in browsers, so that SSR builds work properly now.

Capture UI

• The showErrorDialog option now works properly
• Updated the capture animations
• The z-index of floating elements can be configured by overriding the --mb-z-index-root CSS custom property
• Added mb-logo class to the Microblink logo for customization purposes
• Fixed inherited font color in the camera selector

v1.0.8

Bugfix:

• prevent loading cross-origin worker on non-threaded builds

v1.0.7

• Implemented an approach from https://github.com/CezaryDanielNowak/CrossOriginWorker to load workers cross-domain.

  According to spec, new Worker should honor the response's CORS headers
  but this doesn't work in any of the browsers, so an approach was used
  that inlines the fetched resources inside a Blob and a ObjectURL so
  that they execute from the same domain.

  Note, that this approach won't work with certain CSPs and is not
  recommended. It also may break at any point as it's skirting around some
  pretty undefined browser behaviours.

  The recommended way is still to host the resources and the SDK on the
  same domain.

• Fixed an issue where React refs weren't a valid target for UiSettings.target.

  • Updated JSdoc for createCaptureUI
  • Updated React example to use UiSettings.target

v1.0.5

What's Changed

• Remove dependencies from published package by @ivancuric in #1

Full Changelog: https://github.com/BlinkID/capture-browser/compare/@microblink/capture@1.0.4...@microblink/capture@1.0.5

v1.0.4

Full Changelog: https://github.com/BlinkID/capture-browser/compare/@microblink/capture@1.0.3...@microblink/capture@1.0.4