my qwik app throws error while using <Link> but the same app works fine when using <a> I use loader$ for data fetching.
#Error: element must be connected to the dom while using <Link>
delicate frigate
delicate frigate
should I use prefetch?
zealous jetty
I cope with that one too; forgot how I got it of it
let me know if you figure it out 🙏
delicate frigate
have you used <Link> for PWA/SPA capabilities, while encountering the issue?
zealous jetty
not Link specifically
delicate frigate
in my case iam trying to navigate qwik app using <Link>
zealous jetty
🤔
in my case; I presumed it came from async rendering issues of component / dependencies
graceful mantle
I have the same, rendering components dynamically. But I can't reproduce it on a stackblitz, it's very weird. Unfortunately we have no reference which component is giving us this trouble
graceful mantle
Hi guys, I can pinpoint it to context on top changing rerendering components in a map that contain the same context as the context changing the map. Have you tried previewing? It looks like the preview is not affected.
proper warren
Hi guys, I can pinpoint it to context on top changing rerendering components in ...
I haven't been able to pinpoint it in my case, but I have noticed that it only happens in dev, never in preview or production. So I've just kinda ignored it for now 
graceful mantle
I haven't been able to pinpoint it in my case, but I have noticed that it only h...
LOL. Yeah not gonna happen for me, as this is on all list pages in our ecommerce store front rendering dynamic campaigns. So it breaks while clicking through the shop in dev mode
proper warren
ouch yeah - definitely could use a fix
lunar sierra
Hi guys, I can pinpoint it to context on top changing rerendering components in ...
I can confirm this
graceful mantle
@lunar sierra is your use case complex or are you able to copy paste most parts to a Stackblitz?
I crossing my fingers that this PR https://github.com/BuilderIO/qwik/pull/3307#issue-1615689305 is fixing all our troubles, but It would be better to have something to show anyway
lunar sierra
@graceful mantle My example is a little complex, but I will try to simplify it once I come back from work. The biggest problem is that I don't know which component (or module) is causing this issue so it may take a while 😄
But it follows the context that you mentioned above
graceful mantle
@lunar sierra hmm, I'm not sure if I have time, but maybe we can catch up, I can pin-point it to one component and tried to create a stackblitz with the same structure. Turned out, the issue is not popping up
What timezone are you in?
graceful mantle
perfect, it's the same. If you like we can take a look tomorrow afternoon?
lunar sierra
Tomorrow I will be available a little later, around 21:00 so if it's ok for you
graceful mantle
Or we wait until 3307 get's merged. From my point of view, my code is correct and follows the qwik model
lunar sierra
I'm fine with that too 😉
graceful mantle
But just interested, are you mapping through data, then wrapping a component which conditional renders a component which consumes the same context which causes the rerender?
lunar sierra
All above that you mentioned except I'm not mapping trough data - I am projecting the form steps inside multistep component and each form step component uses the context provided in multistep (parent component)
And then conditionally rendering form steps inside based on index
calm moss
Haha, I've literally just implemented that pattern too.
Had to double take to see if that was my code 😅