- From: James Ingram <j.ingram@netcologne.de>
- Date: Wed, 20 Nov 2013 14:26:04 +0100
- To: public-audio-dev@w3.org
Hi, I'm trying to make a version of my application [1] which will work offline. This is important, because I want to use it during live performances, and can't rely on the internet being available at all venues. So I need to work with local files. As far as I can see, the only way to load local files into a web page in Chrome is to deliver them inside a Chrome extension. But Chrome extensions can't share variables (e.g. midiAccess) with the JS on the main page, so I need to call navigator.requestMIDIAccess() inside the extension. But navigator.requestMIDIAccess() isn't defined there, so I'm stuck. I see no reason why navigator.requestMIDIAccess() shouldn't be defined inside an extension. There's no more security risk accessing midi devices there than anywhere else. Maybe it's just an oversight? Any ideas? All the best, James [1] http://james-ingram-act-two.de/open-source/assistantPerformer/assistantPerformer.html
Received on Wednesday, 20 November 2013 13:26:37 UTC