Alex Lohr
Alex Lohr
That's actually the normal browser behavior. You can use the getSelectionRange/setSelectionRange API to fix the cursor position after input manually (be sure to calculate the correct position if you added...
I think a selection primitive might be a solution. It's on my todo list, but not too far up.
It might interest you that a PR for a selection primitive just landed in @solid-primitives, soon to be released. You'll be able to use it like this: ```ts const [selection,...
`@solid-primitives/selection` is now published, so you can use it.
I don't have a specific workaround. Can you provide a test case to make sure I'm not missing something?
I've just added a test to my local version: ```ts test("For does not need a parent wrapper", () => { const { getByText } = render(() => {(i) => {i}});...
This might be a misunderstanding. The id is only valid for a position inside the shared component tree. Inside the same position, you should always get the same id, both...
It's meant to provide hydration IDs. You can use it for other things as well, but not for multiple unique IDs within the same component. And you're right, it's really...
That's for the core maintainers to decide. Maybe we could add an optional parameter to add a general id functionality to this function, I'm not sure. It's certainly a valid...
I'm currently fixing the vite-plugin so you should be able to get by without extra configuration in the upcoming version (except for globals, if you use them).