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

Re: DOMString-like objects for the CSSOM

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 19 Feb 2010 11:15:43 -0500
Message-ID: <4B7EB92F.10702@mit.edu>
To: "Mark S. Miller" <erights@google.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
On 2/19/10 11:06 AM, Mark S. Miller wrote:
> Why make your new object be String-like rather than simply containing a
> string as a member?

I think the reasoning is tat people use |foo.style.top| as a string 
right now.  So if we want to allow doing |foo.style.top.px = 200| and at 
the same time allow people to treat foo.style.top as a string, then it 
needs to be string-like in some sense.

I suspect that just having it toString to the string it is right now is 
not sufficient for web compatibility.

> Why use is-a rather than has-a?

Because we're trying to extend a legacy API which currently uses 
strings, not designing in a vacuum.

Received on Friday, 19 February 2010 16:16:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:02 UTC