-
-
Replying to @really_bz2 replies 0 retweets 0 likes
-
Replying to @domenic1 reply 0 retweets 0 likes
-
Replying to @really_bz
@bz_moz@annevk Direct proxies have been carefully designed to prevent invariant-breaking of this sort, for extension-prevented objects.2 replies 0 retweets 0 likes -
Replying to @domenic1 reply 0 retweets 0 likes
-
Replying to @really_bz
@bz_moz@annevk "check whether all sealed target properties are present in the trap result" + the invariant enforced by `seal`.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@annevk I was specifically talking about after you did `Object.seal(weirdDomObject)`. (Misspoke earlier and said preventExtensions.)1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@annevk Object.seal(weirdDomObject) throws TypeError. See http://dev.w3.org/2006/webapi/WebIDL/#indexed-and-named-properties … paragraph 5.2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@annevk Cool, I had only seen https://www.w3.org/Bugs/Public/show_bug.cgi?id=22320#c11 … which seemed to imply there was no specified behavior for sealing.1 reply 0 retweets 0 likes
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.