It’s actually not the developers’ fault — Chrome has non-standard features not available in other browsers. As I was reading through the comment thread it seems

It’s actually not the developers’ fault — Chrome has non-standard features not available in other browsers. As I was reading through the comment thread it seems like in this case, it’s the MIDI API. This of course presents potential developers with a dilemma: develop an application using the exclusive API and therefore lock the user to that browser or don’t develop it all due to lack of cross-browser support? In essence this is not dissimilar to choice companies used to have to make when developing IE-specific enterprise applications, only the reason was more nuanced; Because of the sheer ubiquity of IE, it made sense to develop to that platform and accept its quirks and features, or not develop it at all, since developing cross-browser compatible applications could be prohibitively expensive and time consuming, if it was even possible.