Re: Audio-ISSUE-104: Define a security model for requesting access to the MIDIAccess interface [MIDI API]

1. Did we ever discuss, in the port over to Bugzilla, how to use Issues in
Tracker vs. bugs in Bugzilla?  I'm no longer sure where to address things.

2. For example - the new text on getMIDIAccess() is very Draconian, copied
from getUserMedia(), that the UA MUST prompt the user for access.  I think
this is probably overkill for MIDI; although I do believe we shouldn't just
let MIDI interfaces be always accessed without notification, I think in
many situations I'd rather not be prompted (e.g. this could probably be
cached for a given web application, that I've approved it.)  I think we
should leave this more to the interpretation of the UA - that prompting MAY
happen, not MUST.

On Wed, Jun 6, 2012 at 7:56 AM, Jussi Kalliokoski <
jussi.kalliokoski@gmail.com> wrote:

> On Wed, Jun 6, 2012 at 5:49 PM, olivier Thereaux <
> olivier.thereaux@bbc.co.uk> wrote:
>
>> Hi Jussi,
>>
>> On 6 Jun 2012, at 15:11, Jussi Kalliokoski wrote:
>>
>> > This issue is now pending review per
>> https://dvcs.w3.org/hg/audio/rev/1ab2a972b9bc .
>>
>> I've edited the issue and its bugzilla counterpart:
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17417
>>
>>
>> > P.S. It seems that I can't log in to our bugzilla. Do I need another
>> login than my W3C login?
>>
>> Yes, you need to create a separate account here:
>> https://www.w3.org/Bugs/Public/createaccount.cgi
>>
>> Olivier
>
>
> Great! Thanks Olivier!
>
> Cheers,
> Jussi
>

Received on Wednesday, 6 June 2012 17:02:43 UTC