Yes, very much regrettably, I now find myself using Chrome when I really would like to avoid that. But unfortunately there is no way around this right now that I've found to be reliable enough and easy enough to the point that I would advise users to go that route. Sorry.

Note this 8(!) year old bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=836897

It's embarrassing.

> Mozilla is too busy improving the world instead of their browser and WebMIDI is not supported

That is misleading. Mozilla chose not to implement it for security concerns. More context: https://github.com/mozilla/standards-positions/issues/58#iss...

Security concerns that Chrome seems to be able to deal with just fine. If that's the issue then block sysex but allow the rest, the midi (v1) protocol isn't that hard.

Meanwhile, there are 100's of WebMIDI capable applications now and Mozilla still claims there is no demand for a feature they do not support. That's backwards, of course a feature that you do not support is not in demand because people simply go elsewhere.

The cumulative effect of a lot of little crappy decisions like this is part of why FireFox' market share eroded (the other is Google's anti competitive behavior).

> Unfortunately, because Mozilla is too busy improving the world instead of their browser and WebMIDI is not supported on Firefox you have to use Chrome