On 2/18/14 4:34 PM, Allen Wirfs-Brock wrote:
In that case, i don't see why the DOM is a barrier to adding @@create to JS.
It's not, and I'm not quite sure where you thought I said it was....
I was talking about actual uses of subclassing for DOM objects.
Maybe we should make DOM constructors behave sort of like the Array
constructor, of course...
Do you really think you can deprecate exist call without new instantiation
behavior?
Maybe. Unclear. Right now, WebKit (and Blink) doesn't support calling
DOM constructors without "new" and never has. Trident and Gecko do and
always (at least as far back as I can test) have.
So we can deprecate it to the extent that web sites don't run different
code in different browsers.... Some people are more worried about this
than others, of course.
Are you saying that it isn't de-facto standard behavior and so there is a hope
of getting rid of it.
It's unclear; see above.
You don't necessary need a new slot to to use as an initialized flag. I most cases you
can probably get away with using a "not yet initialized" token in some existing
slot.
While true, doing that requires per-object-type whack-a-mole that we
don't really want to force DOM spec authors into....
-Boris
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
