@davidbaron @khuey_Well, normal interface props live on protos. Should polyfilling EventTarget break for the global, for example?
-
-
Replying to @really_bz
@bz_moz WebIDL interfaces are uniform that way, agreed. Global is special. How would polyfilling "own" EventTarget break?@davidbaron@khuey1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@davidbaron@Khuey If I set EventTarget.prototype.addEventListener, should it affect window.addEventListener? Imo, it should.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz IOW, proto-methods should be in prototypes; data vars like mozIndexedDB should be in global; WebIDL has to cope.@davidbaron@Khuey2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@davidbaron@Khuey Putting proto-methods on protos means object-detection of, say, requestAnimationFrame has the same problem.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz Does anyone do such detection and capture the result in a var of the same name? I think not.@davidbaron@Khuey2 replies 0 retweets 0 likes
@BrendanEich @davidbaron @khuey Sure they do, for requestAnimationFrame. Mostly in functions that I saw, just like they do it for indexedDB
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.