This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20509 - SHOULD/MUST user permissioning mismatch
Summary: SHOULD/MUST user permissioning mismatch
Status: CLOSED INVALID
Alias: None
Product: AudioWG
Classification: Unclassified
Component: MIDI API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Wilson
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-24 08:21 UTC by Marcos Caceres
Modified: 2013-01-18 15:51 UTC (History)
2 users (show)

See Also:

Attachments

Description Marcos Caceres 2012-12-24 08:21:52 UTC 
The spec says:

"This call *SHOULD* prompt the user for access to MIDI devices. If the user gives express permission or the call is otherwise approved, successCallback is invoked, with a MIDIAccess object as its argument."

But then it says:
[[
"When the requestMIDIAccess method is called, the user agent *MUST* run the following steps:"
...
7. Prompt the user in a user-agent-specific manner for permission to provide the entry script's origin with a MIDIAccess object representing control over user's MIDI devices.
]]

I think the first assertion should be dropped (i.e., delete "This call SHOULD…"). And in 7. the word "optionally, " should be prefixed to the step.
Comment 1 Chris Wilson 2012-12-26 18:36:41 UTC 
Actually, this is already handled - step 6 may optionally jump to the success step.  Step 7 is only reached if the UA does not wish to prompt.
Comment 2 Olivier Thereaux 2013-01-18 15:51:00 UTC 
Batch-closing RESOLVED MIDI issues. Reminder: midi issues now tracked at https://github.com/WebAudio/web-midi-api/issues