[whatwg] [Notifications] Constructor should not have side effects

Ian Hickson ian at hixie.ch
Tue Jan 29 12:32:19 PST 2013


On Tue, 29 Jan 2013, Elliott Sprehn wrote:
> On Tue, Jan 29, 2013 at 3:02 PM, Ryosuke Niwa <rniwa at apple.com> wrote:
> >
> > ... Is that even a valid use case? It seems dubious to instantiate a 
> > class named "request" and then not send a request.
>
> You can't go down that line of thinking because it doesn't generalize. 
> For instance why would I instantiate a class named "node" without 
> putting it into the tree?

There are all kinds of reasons why you may do this. Hence, we support it.

Reasoning by use case definitely generalises -- it's how we design 
everything around here. :-)


> If we followed that logic then new HTMLDivElement should append itself 
> into the document by default.

A more apt example would be the way <audio>, when constructed with a URL, 
immediately starts loading it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'



More information about the whatwg mailing list