Closed Vichondrias1 closed 1 year ago
Before 5.2.0
it's not possible to fix.
In 5.2.0
I added new property positionResolver
where you can pass your own floating position resolving function. Svelty-picker uses floating-ui itself, so you can use it for your own resolver. It already provides detectOverflow function, which will be required to handle your use case properly.
Before
5.2.0
it's not possible to fix.In
5.2.0
I added new propertypositionResolver
where you can pass your own floating position resolving function. Svelty-picker uses floating-ui itself, so you can use it for your own resolver. It already provides detectOverflow function, which will be required to handle your use case properly.
can u give example how to use that new property you added?
can u give example how to use that new property you added?
Just like any other prop:
<script>
function myPositionResolver(node) {
// your code
}
</script>
<SveltyPicker positionResolver={myPositionResolver} />
If you have no idea how the resolver should/could look like, check the built-in position resolver:
And build your own on top of it with detectOverflow helper function etc.
<SveltyPicker positionResolver={myPositionResolver} />
is it neccessary to add positionResolver function to fix my problem or the build in function you added should fix problem it and i dont do anything?
is it neccessary to add positionResolver function to fix my problem or the build in function you added should fix problem it and i dont do anything?
Yes, it is neccessary to add positionResolver for your use case
@Vichondrias1 were you successful with implementing your own resolver?
i havent figure it out how to use it can you please help me how solve this? dont quite understand sa how to fix this
I gave you all information you need.
My time is precious so I can't help you for free. I believe you understand.
Anyway I am closing this one as root issue - ability to customize position resolver is fixed now.
How to fix this when I try to add svelte picker on a container in tailwind the calendar doesnt go outside the container.
I was expecting the calendar to be like this.