W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

[Bug 16450] New: Class String

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Mar 2012 15:42:52 +0000
To: public-script-coord@w3.org
Message-ID: <bug-16450-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16450

           Summary: Class String
           Product: WebAppsWG
           Version: unspecified
          Platform: DEC
        OS/Version: Neutrino
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
        AssignedTo: cam@mcc.id.au
        ReportedBy: w3c@marcosc.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-script-coord@w3.org


If class string is an internal property of an object, then it should be defined
as [[ClassString]] to be consistant with ECMAScript. It's confusing to bounce
from conceptual definitions to object property definitions. Also, there is a
pattern to expose all internal properties of an object in ECMAScript5. I think
it should be the assumption that Class String will also eventually be exposed
to script (or should be explicitly defined to be!). 

If anything, for sanity, give the class string contant names:

platform object: "Platform"
interface prototype object: = "Prototype"
exception interface prototype = "Exception"

or some such. This would be consistant with the use of ECMAScript5 Type(x). In
the case of WebIDL, it should be referred to as ClassType(x), then in prose: 

 If ClassType(x) is "Platform"...

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 20 March 2012 15:42:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC