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

[whatwg] WebIDL vs HTML5 storage changes

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Tue, 20 May 2008 20:35:48 +0200
Message-ID: <C520CA9514F04D908299FD37EF317B6B@POCZTOWIEC>
Opacity of style is not quite the same thing because you compare a
predefined property to an expando property.  Predefined properties should
not be deleted, deleting expando properties should be supported.


-----Original Message-----
From: whatwg-bounces@lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Maciej Stachowiak
Sent: Tuesday, May 20, 2008 5:50 AM
To: robert at ocallahan.org
Cc: Brady Eidson; WHATWG Mailing List
Subject: Re: [whatwg] WebIDL vs HTML5 storage changes

On May 19, 2008, at 4:54 PM, Robert O'Callahan wrote:

> If "storage.keyName = 'value';" can create a new storage item  
> (persistently), won't authors expect "delete storage.keyName;" to  
> remove it (persistently), as a matter of consistency?
> If overloading "delete" is too quirky or too hard to implement, then  
> it seems none of the other shorthands should be allowed either.

Many objects in the DOM implement custom name getters (for instance  
NodeList) and a few even implement custom name setters  
(CSSStyleDeclaration, at least the way it is done in WebKit) but no  
one has clamored for a custom deleter or expected delete to work "as a  
matter of consistency" or been confused that "style.opacity = 0" is  
allowed but "delete style.opacity" is not. So I would say the  
available evidence argues against your conclusions.

Received on Tuesday, 20 May 2008 11:35:48 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:02 UTC