Regression in v3.12.0 - Cannot resolve a Slate point from DOM point: [object Text],0

[SiddharthSham]

Describe the bug

On v3.12.0, focusing the cursor in any Portable Text Editor field throws the following error:

Cannot resolve a Slate point from DOM point: [object Text],0

This used to work perfectly in v3.11.5, so it must be a regression in v3.12.0

To Reproduce

1. Ensure you are using version 3.12.0
2. Create a Portable Editor Field
3. Attempt to type in any content / focus the cursor

Expected behavior
Content can be input

What operating system are you using?
MacOS Ventura 13.4 (22F66)

Which versions of Node.js / npm are you running?
v18.14.2

Additional context
The problem seems to originate from Slate, so it might be a quickfix to rollback to a working version.

[bobinska-dev]

Hello @SiddharthSham 👋
Could you update your sanity versions and see if this error persists? We are not able to recreate this....

[SiddharthSham]

Hello @bobinska-dev , I did test this last weekend with v3.14.1 as well, and I confirm the error still exists with PortableText :(

[umxr]

@SiddharthSham Are you getting this error with a custom input? or just the native portable text block. im having the same issue. in my case, we have a custom input

[SiddharthSham]

@umxr I get the error regardless of whether a custom input is being used or not. However, I did first notice it when using a custom input (for field-level localisation). Are you able to get rid of this error by removing the custom error, by any chance?

[d4v1d82]

@bobinska-dev @umxr I can confirm I have the same issue while using sanity-plugin-internationalized-array with portable text. You can also check the issue in the project sanity-io/sanity-plugin-internationalized-array#15 that refers to the problem.
The error is not present in v3.11.5 but is present from v3.12.0

[umxr]

@d4v1d82 I recently checked with v3.14.1 and still had the issue

[d4v1d82]

Sorry @umxr wrong copy/paste, I've updated the comment with the right version that is 3.11.5

[SimeonGriggs]

This error, when seen in the Internationalized Array plugin, is fixed in version 1.10.0

[SiddharthSham]

I see the error is resolved when all the props are passed to the member, thanks to @SimeonGriggs for helping figure that out!

[github-actions]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.