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

[Bug 16457] New: IDL exceptions as platform objects

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

           Summary: IDL exceptions as platform objects
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            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


I'm a bit confused as to why "objects representing IDL exceptions" are
considered "platform objects". It is possible to construct and throw such IDL
exceptions in ECMAscript without it being a platform object. This makes IDL
exceptions indistinguishable from platform objects. 

I'll also note that the whole notion of platform objects and that they can only
be distinguished by  a magical inaccessible internal property shuts out
JavaScript only implementations (which seems to go a bit against the spirit of
ECMAScript, which exposes most of its guts to developers). That seems bad :( If
this is the case, then there should be a isPlatformObject() method defined on
Object. 

//true
var foo = Object.isPlatformObject(Node)

-- 
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 19:15:56 UTC

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