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

Re: DOMString-like objects for the CSSOM

From: Brendan Eich <brendan@mozilla.org>
Date: Fri, 19 Feb 2010 17:33:58 -0800
Cc: Simon Pieters <simonp@opera.com>, Boris Zbarsky <bzbarsky@mit.edu>, "Mark S. Miller" <erights@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-Id: <F56349CF-1EF3-4CF0-B0C8-84E6216C1C1C@mozilla.org>
To: Maciej Stachowiak <mjs@apple.com>
On Feb 19, 2010, at 5:27 PM, Maciej Stachowiak wrote:

> We definitely do need an API that works with numbers. Conversion, no  
> matter how optimized, is a waste. Furthermore, it's not just a  
> simple conversion, the units part of the string must be removed and  
> then re-added. I don't think there is any question that we need to  
> bypass all that and enable direct use of numeric values.

Ok, sure -- I'm not denying API needs, just redirecting them :-/.

> The question is just whether to hang it off the string-based API in  
> this slightly odd way, or to add a new parallel API. Please don't  
> throw out the valid use case baby with the quirky solution bathwater.

Not throwing out use-cases.

> My design taste and compatibility concerns would lean towards a new  
> parallel API, but I'm willing to give proponents of extended strings  
> a chance to demonstrate that it is a viable option.

Compatibility is pretty much all or nothing. Trying to cheat requires  
massive field testing, and even then you may not hear bad news until  
next year. Why risk this kind of breaking change actually breaking  
some important web content?

Received on Saturday, 20 February 2010 01:39:14 UTC

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