Rousseau Julien

Of course, if we use fixtureSync with scoped elements like this: ``` const el = fixtureSync(fixtureData, { scopedElements: { 'dt-contract-header': DtContractHeader, }, }); ``` Then we have this error: fixtureSync...

Hello @bahrus, I have added min and max properties and also a disabled-days property. You can see the updated demo : [here](https://roxus.github.io/range-datepicker/components/range-datepicker/demo/)

+1 Same issue here

@timur560 I made a fork which avoid the dom changes, so the issue is solved (only in this case of we use an API to apply the sort). See https://github.com/RoXuS/sortable-list/commit/555c68c3d83b46c7ab8eb1db33829f55057738d7....

or maybe an option to pick the first nvim instance OR pick the closest (in current window then in closest window)?

oh ok and this feature is possible, can we selected the "closest" vim instance?

Here we haven't this issue with following code: (lit 3.1.4) ```ts describe('dt-die-documents-card-type-render', () => { afterEach(() => { document.querySelector('dt-die-documents-card-type-render')?.remove(); }); it('BPU', async () => { const fixtureData = html``; render(fixtureData,...