fix: separate the internal ref from the external one for correct operation of useImperativeHandle and getBoundingClientRect

[exzos28]

Summary:

1. Passing a ref causes a crash in the web:

Here, a single ref is used both for working with useImperativeHandle and for obtaining the position via getBoundingClientRect.

However, when calling getBoundingClientRect, the ref does not exist. It is likely that the implementation of useImperativeHandle has changed in React19 and its createHandle callback overrides current.

2. Fix updateValue via ref - always call the onValueChange callback.

Test Plan:

I've create an ControlledSliderExample in src/Examples:

Screen.Recording.2025-10-14.at.15.12.43.mov

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Ref Typing Issue Breaks DOM Access

The forwardedRef no longer provides access to the component's DOM element, instead only exposing the updateValue imperative handle. This breaks consumers expecting DOM access (e.g., getBoundingClientRect). The internal containerRef is typed as HTMLElement but requires as any when assigned to the View component, indicating a type mismatch and bypassing type safety.

 

[rosko]

Stupid comment. forwardedRef never provided DOM access, and it was replaced by the imperative ref handle.

[exzos28]

anyone?

[rosko]

up