so this mean that freezing a Contructor.prototype to enforce/ensure nobody can change runtime that prototype will result in unusable code as we know, right? Or we should never pre define properties that should be changed runtime? Second one works and stink at the same time.<div>
<br></div><div>I preferred the old V8 behavior ... if I freeze a __proto__ the object should not pass through that proto when a property is set unless the proto has a setter ... but this is another story I guess.</div><div>
<br></div><div>Anyway, thanks for explaining this which is gold for a blog post.</div><div><br></div><div>br</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 6, 2012 at 1:46 PM, Brandon Benvie <span dir="ltr"><<a href="mailto:firstname.lastname@example.org" target="_blank">email@example.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Clarification: if an object has no own property, then it defers to the writability from the prototype chain. If it has an own property then it never checks the prototype chain.