W3C home > Mailing lists > Public > public-media-capture@w3.org > June 2014

Re: [Bug 26062] New: fixing the description of the "_readonly" attribute on MediaStreamTrack

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 12 Jun 2014 06:08:35 +0200
Message-ID: <539927C3.8040709@alvestrand.no>
To: public-media-capture@w3.org
On 06/11/2014 07:16 PM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26062
>
>              Bug ID: 26062
>             Summary: fixing the description of the "_readonly" attribute on
>                      MediaStreamTrack
>             Product: WebRTC Working Group
>             Version: unspecified
>            Hardware: PC
>                  OS: Windows NT
>              Status: NEW
>            Severity: normal
>            Priority: P2
>           Component: Media Capture and Streams
>            Assignee: public-media-capture@w3.org
>            Reporter: shijuns@microsoft.com
>                  CC: public-media-capture@w3.org
>
> MediaStreamTrack has an attribute in its interface definition called
> "_readonly" (including the underscore).  However, the description refers to it
> as simply "readonly".
>
> Re the underscore, we had this explained as being a workaround for the fact
> that readonly is a reserved word in WebIDL.
>
> With a bit digging: the May-29-2013 version of the GUM spec has the underscore
> in the description.  It was removed in the July-2013 update.
>
> It should be added back to make the spec self-consistent.
>

According to previous discussion, the WebIDL specification says that 
when the WebIDL is mapped  to Javascript, initial underscores disappear.

So the description is consistent with what a Javascript programmer would 
use.

CamelCase avoids the semantic confusion, though.
Received on Thursday, 12 June 2014 04:09:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:28 UTC