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

[Bug 16537] Interface types - Implements is ambiguous

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Mar 2012 23:12:04 +0000
To: public-script-coord@w3.org
Message-Id: <E1SCfYa-0006rc-S1@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16537

--- Comment #8 from Marcos Caceres <w3c@marcosc.com> 2012-03-27 23:12:03 UTC ---
(In reply to comment #7)
> "correct" in what sense?  The point is that it should return whatever your
> actual DOM implementation considers to be an implementation of I.  Since the
> resulting value is never exposed directly to user script, and in fact may well
> not even be a value in JavaScript if your DOM implementation is in some other
> language, what sort of interoperability are we talking about?

Sorry, maybe I'm getting confused because I am implementing it as a user
script. My understanding is that this algorithm is used when I have the
following: 

interface Foo{
   attribute Bar? pub; 
}

[Constructor]
interface Bar{}

//Then... in JS land.... 
var placeToDrink = new Bar(); 

someFooObj.bar = placeToDrink; //this is ok, do what the spec says. 

someFooObj.bar = "The pig and whistle"; //throws TypeError

-- 
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, 27 March 2012 23:12:07 UTC

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