If you can isolate that DOM performance bottleneck or point me to a live example, I'm happy to pare it down to a minimal test case and make sure it gets fixed.
(We have some enormous architectural changes inbound which should help, but I'd still love to make sure we have a test to prevent regressing)
In Chrome it's buttery smooth on any decent computer made in the past 5 or 6 years. In Firefox it's usable on a powerful computer, but notably worse than Chrome.
On an under powered laptop Chrome is still very usable, not quite 60fps, but probably 30-40fps on moderately complex designs.
Firefox is a choppy mess on low end hardware.
This is a recurring issue with Firefox. It's just ok for regular web browsing, and it's a hot mess for any web app that needs to do any moderately taxing DOM manipulation.
As much as I love Firefox, it's just leagues behind Chrome in regard to performance.
(We have some enormous architectural changes inbound which should help, but I'd still love to make sure we have a test to prevent regressing)