2.0.0-rc.6: SSR produces invalid textarea value

[dangkyokhoang]

Describe the bug

This pattern <textarea {...{ "data-x": "x" }} value={val()} /> renders <textarea value='something' /> instead of textarea with text content.

Your Example Website or App

https://stackblitz.com/edit/nitrojs-nitro-leuuhgqk?file=src%2FApp.tsx

Steps to Reproduce the Bug or Issue

Go to the link above

Expected behavior

Should render valid textarea value.

Screenshots or Videos

No response

Platform

Additional context

No response

[javascript-unsafe]

Reproduced on 2.0.0-rc.6 and the prior next base.

1. SSR-render <textarea {...{ "data-x": "x" }} value={value()} />.
2. The merged props reaching ssrElement contain both data-x and value.
3. The generic SSR prop loop serializes value as an HTML attribute, producing <textarea ... value="something"></textarea>.

Normal textarea attributes are compiler-rewritten into text content, but elements with a spread use ssrElement directly. The fix applies the same value/defaultValue → text-content rule to that runtime path, with coverage for spread order and source variants: #3287

[ryansolid]

Fixed in b64071c (#3287): when a spread forces runtime serialization, `ssrElement` now folds textarea `value`/`defaultValue` into the element's text content, matching what the compiler does statically. Lands in the next RC.

— Claude via Cursor