Ben Kremer

Hi @VovaCHTB, Great point 👍 Thank you for adding the image, really demonstrates what the problem with the fixed Node/ForeignObject ratio is. I had a quick think through this and...

Hi @LunarAI, thanks for making me aware of this issue in v2. I've created a small repro attempt with a (simplified) data fetch here ([codesandbox.io](https://codesandbox.io/s/rd3t-v2-issue-330-repro-1xpvs?file=/src/App.js)). By default the tree seems...

No need to apologise 😄 Thanks again for bringing my attention (back) to this, since it's a use case that should get first-class support instead of requiring workarounds due to...

Hi @stevepetebruce, February was a super busy month for me both in- and outside of work, but I had some time this weekend to look more deeply into this topic...

Yeah the `initialDepth` functionality is pretty rudimentary as it stands currently. It also doesn't do what you expect with async loaded data via `treeUtil`, i.e. it won't apply `initialDepth` once...

@RohanDamani Hmm I think that's expected behaviour for setting `siblings: 0.5`, since the number represents a factor of node width. As in `siblings: 1, nonSiblings: 2` would mean "separate sibling...

Hi @KrzysztofKarol, thank you for reporting this! I was actually unaware of how/if this library worked with SSR. The source doesn't make any reference to `document`/`window`, so seems to be...

Ahh interesting, thanks for digging into this already. Seems like the least path of resistance would be to set `options.singleton` if it's part of the `style-loader` public API since [IE...

Ok cool, good to hear you found a way. If `isomorphic-style-loader` seems to do the job I'll move the build pipeline to that. Ok that's a strange one regarding `react-transition-group`,...

Hi @codemonkeycxy, SSR still isn't technically supported. I spent an entire day at the time tinkering with the isomorphic loader that Krzysztof suggested (and one or two other ones). I...