Mohit Cheppudira

So firstly, I hate the current positioning mechanism, and really wish that I had put in well-defined anchor points from the start. I like your idea better, because you have...

Yes, agreed. A few years ago, I started work on a `Container` class, which abstracted away the grouping logic because I wanted to build a new `StaveContext` for cross-stave formatting......

I wanted to change all the documentation to use Factory instead of raw vexflow classes. There's a bunch of places this needs to be done: e.g., https://github.com/0xfe/vexflow/wiki/The-VexFlow-Tutorial

Yes, that's totally incorrect. Will fix.

Thanks for letting me know.

Hi -- I've seen this kind of issue come up with Vexflow/React. It's most likely the virtual DOM getting in the way. Instead of `const chordDiagram = new ChordBox('#canvas', ...)`,...

Did it start working locally after the change I suggested? Or before too?

Hi Joanne -- I spent some time digging into this and it looks like React really takes over the entire DOM, making it tricky to do the type of dynamic...

My hypothesis: React uses a Virtual DOM, which is a shadow in-memory structure that represents the DOM. This is ostensibly faster than manipulating the DOM directly, and is enabled only...