3 ms·

I guess the reason is probably that it probably requires a developer with a midi device, and it affects too few users for Mozilla to want to prioritise it. The

I guess the reason is probably that it probably requires a developer with a midi device, and it affects too few users for Mozilla to want to prioritise it. The bug currently has priority P3. There are about 8300 existing P1 and P2 bugs, and over 10000 P3 bugs. Saying that it works in chrome, brave, opera, edge etc sounds like “look at all these other vendors who put the effort in” but really they are all running the same code these days so you could instead write “chromium implements it”.

boomlinde 7y ago
> I guess the reason is probably that it probably requires a developer with a midi device That is not true at this point. AFAIK Windows, OS X and ALSA all support virtual MIDI devices. Windows and OS X (last time I used it) ship with virtual General MIDI outputs and there is a lot of free third party software for virtual input. I'd rather say that the reason is probably that you need a developer with domain knowledge and interest, and a consensus on what the standard should include.