Skip to content

@ebitex/forms-sdk

Changes to the Forms SDK and its React form component. Newest first. How versions work is on Releases and versions.

2026-11-06 — The form component moves focus to the first problem, and its wording is yours

Section titled “2026-11-06 — The form component moves focus to the first problem, and its wording is yours”

@ebitex/forms-sdk 1.1 changes what <EbitexForm> does around an error. All of it is additive; the only visible change for a form that passes no new option is the behaviour below.

  • Focus and a summary. After a step or submit fails validation, focus moves to the first field that needs fixing. With two or more, a summary above the step lists them as links. Pass focusOnError={false} to keep the old behaviour.
  • A visible failure message. A network failure or a server error now shows a message and keeps the answers; onError is still called. Pass showErrorMessage={false} if you render your own.
  • Steps. The step indicator is a progressbar (it was a status paragraph) and takes focus when the step changes.
  • labels. Replace any string the package writes (back, next, required, errorSummary, …). FormsLabels is exported.
  • autocomplete and inputMode. Email, phone, URL and number fields set them, and a field definition may carry autocompletePurpose.
  • Dark mode. The default dark theme’s button label is near-black (--ebitex-forms-accent-contrast) so it meets AA. If you styled .ebitex-forms__button or set your own accent, check your dark mode.

See Errors, accessibility and your own wording.

2026-10-18 — Forms can share a page’s visitor

Section titled “2026-10-18 — Forms can share a page’s visitor”

@ebitex/forms-sdk gains sharedVisitorSession, which turns the visitor object a page already has (the one createVisitors returns in @ebitex/visitors-sdk) into a session for <EbitexForm visitor={…}>. The form then sends the page’s token and consent signals, hands what its responses say back to the page’s visitor, and forgets the device everywhere. A form without one keeps its own session, exactly as before, and @ebitex/forms-sdk still has no dependency on the other package. @ebitex/visitors-sdk gains consentSignals() and adopt() for this. See Share one visitor with the rest of your site.

Section titled “2026-10-12 — Forms: visitors are recognized only with consent; @ebitex/forms-sdk stops storing an id”

The visitor on a public form is now identified by an opaque token the API issues, not a UUID you generate, and recognizing a respondent across visits needs their consent. The submit and render requests take an optional consent member (cmp, gpc, dnt, cmpString); the responses carry visitor and consent (including the wording to show). A new forget operation lets a respondent clear their browser. Unsigned UUIDs are still accepted until 2027-01-12.

In @ebitex/forms-sdk, the token is held in memory and never written to localStorage, sessionStorage, a cookie or IndexedDB by the package. Pass a storage adapter to keep it between visits; it is called to save only while recognition is granted. getOrCreateVisitorId, which wrote to localStorage, is removed from @ebitex/forms-sdk/react. See Consent and returning visitors.

These entries are written in full on another page.