Alexander Prinzhorn
Alexander Prinzhorn
> Maybe connectTo is the wrong API to use anyway? Because we're not using the guidesLayoutBehavior instance anyway because the layout engine modifies the layout object directly inside the layout...
the `:detach` event doesn't bubble because the behavior is detached in response to the component being disconnected (hence no parents to bubble to) 🤦♂️
The whole `_observeLayoutDependencies` is a bad idea and needs to be schedule with raf. There is no point in having every LayoutBehavior listen to those events for themselves. We can...
> In theory we could get rid of all these problems by recreating everything when an element is added or removed. This way there would be a guarantee that everything...
This is requested as part of https://github.com/Prinzhorn/skrollr-menu/issues/6 I agree that it would be very helpful.
No it hasn't.
> Have you got an advice for me how this can be debugged best? Use Chrom(e|ium). Set breakpoints (e.g. here https://github.com/Prinzhorn/skrollr-stylesheets/blob/master/src/skrollr.stylesheets.js#L187). Find out stuff.
I just ran into a similar situation where morphdom would just keep adding the same element with every morph because of duplicate Ids. I would really appreciate if there could...
Hey, this looks good. Any news? I'd love to get rid of `ECONNRESET`.
Maybe I've missed it, but could you add integration tests with the example from https://github.com/sveltejs/svelte/issues/8026? So that we make sure it actually fixes the issue with `&rect` inside an attribute?...