CJ Yetman

Ugh... this issue has caused way more hassle than anything else by far... all just to put a newline in tooltips. see #180 #152 #130 #146 #151 #175 #215 #250...

and there's some report here https://github.com/christophergandrud/networkD3/pull/130#issuecomment-232888736 that suggests `\n` is not necessarily the most compatible option

My preference would be to make the default delimiter either ": " or " - " for full, safe compatibility. Then **maybe** add some functionality that would allow a user...

also of note... using 0.4 release version and the 0.4.9000 dev version of `networkD3` on macOS 10.14.3, R version 3.5.2, and RStudio version 1.2.1114... neither (links or nodes) of the...

> If you go this route, then instead of adding the arguments I suggested above for backward compatibility, I would consider adding the ability to provide custom JavaScript functions to...

I think this is a reasonable suggestion, even if not as easy to implement as it may sound. Would anyone miss the old behavior? Not sure it would be worth...

That ability is not built in, but there are a number of workarounds on Stack Overflow, e.g. https://stackoverflow.com/a/45495841/4389763 Building this in would not be trivial, but maybe someone would be...

I'm willing to put some work into this, but it would be more appealing if there was an obvious need. Can anyone provide a plausible, reproducible example where the performance...

1. To set a reasonable benchmark (1k or 100k nodes?) 2. For my own personal satisfaction knowing that I'm spending time and effort on something that's actually worthwhile ;-)

(As opposed to chasing some convoluted edge case)