W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2007

[whatwg] Canvas spec issues

From: Darin Adler <darin@apple.com>
Date: Sat, 12 May 2007 09:21:21 -0700
Message-ID: <B6D12E97-49CB-4D18-8591-AE588A28E195@apple.com>
On May 11, 2007, at 4:18 PM, Ian Hickson wrote:

> On Mon, 26 Mar 2007, Philip Taylor wrote:
>
>> A couple of points that are unclear and are causing differences  
>> between
>> current implementations (which is presumably a bad thing):
>>
>> "interface HTMLCanvasElement" says "attribute long width;". #reflect
>> says "If a reflecting DOM attribute is a signed integer type  
>> (long) then
>> the content attribute must be parsed according to the rules for  
>> parsing
>> signed integers first", which seems to apply in this case. But the
>> canvas section says of width/height, "The rules for parsing non- 
>> negative
>> integers must be used to obtain their numeric values". Hence,  
>> conflict.
>>
>> Also, "canvas.width = -1" is acceptable for a signed long, but  
>> doesn't
>> make sense here. (After setting that, Firefox gives canvas.width==0,
>> Opera gives 300, Safari gives -1.)
>
> Changed to unsigned.

If it's unsigned, it's ambiguous what behavior should be when an  
attempt is made to set the value to a signed value via JavaScript.  
Should an INDEX_SIZE_ERR exception be raised? Should the value be  
ignored?

I think I ran into this problem with HTMLOptionsCollection length  
property.

     -- Darin
Received on Saturday, 12 May 2007 09:21:21 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:55 UTC