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 23817 - [Nit] Redundant TOC headers 8.1 & 9.1
Summary: [Nit] Redundant TOC headers 8.1 & 9.1
Status: CLOSED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 02:20 UTC by Travis Leithead [MSFT]
Modified: 2014-05-08 17:53 UTC (History)
4 users (show)

See Also:

Attachments

Description Travis Leithead [MSFT] 2013-11-14 02:20:10 UTC 
Both Section 8.1 and 9.1 are titled "NavigatorUserMedia", might want to differentiate these.

I'd recommend 8.1 be "getMediaDevices" and 9.1 be "getUserMedia".
Comment 1 Adam Bergkvist 2013-11-21 12:02:56 UTC 
Both these sections contain an idl interface. That means that Respec.js will automatically generate a subsection called "Methods".

?.? getMediaDevices
   ?.?.? Methods

That looks a bit strange.

The first section defines the NavigatorUserMedia interface, and the second adds an other method to it. How about:

"NavigatorUserMedia" and
"NavigatorUserMedia Interface Extensions"

We use that pattern in the webrtc spec when we add, e.g., createDataChannel() to RTCPeerConnection in the separate P2P Data Section.
Comment 2 Travis Leithead [MSFT] 2013-11-21 19:26:43 UTC 
Works for me.
Comment 4 Stefan Hakansson LK 2014-05-08 08:31:19 UTC 
Fixed in http://dev.w3.org/2011/webrtc/editor/archives/20140507/getusermedia.html
Comment 5 Travis Leithead [MSFT] 2014-05-08 17:53:04 UTC 
Thanks!