You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use it in "if" block, it sometimes make the next blade fly away. I'm still finding what cause that. For reproduce, see this:
To reproduce this, you need to put them into a tab, inside an IF block, and have blades and Element in the same time:
<TabGroup>
<TabPage title="A">
<Checkbox label="Check this" bind:value={check} />
{#if check}
<Text label="I should inside if block and before the element" bind:value={text} />
<Element>
Something here
</Element>
<Text label="I should inside if block and after the element" bind:value={text} />
{/if}
<Text label="outer text" bind:value={text} />
<Text label="outer text" bind:value={text} />
</TabPage>
</TabGroup>
and what I want:
what it actually goes:
A text element inside IF block goes next to the outer text element.
The text was updated successfully, but these errors were encountered:
Thank you very much for reporting this and for providing a clear and concise reproduction example.
I think I've fixed the issue, see the latest release v1.3.3. (Feel free to re-open if you find otherwise.)
Maintaining consistent ordering of elements between Svelte's declarative approach in template markup and Tweakpane's imperative approach behind the scenes has been one of the trickier parts of this project. 😅
When I use it in "if" block, it sometimes make the next blade fly away. I'm still finding what cause that. For reproduce, see this:
To reproduce this, you need to put them into a tab, inside an IF block, and have blades and Element in the same time:
and what I want:
what it actually goes:
A text element inside IF block goes next to the outer text element.
The text was updated successfully, but these errors were encountered: