[Bug 17523] Specification should define behavior when immutable values are changed

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17523

--- Comment #6 from Glenn Adams <glenn@skynav.com> ---
(In reply to comment #5)
> Yes? "undefined" there is the JS value undefined, not that it's not defined
> in the spec. That the behavior differs between strict and non-strict
> similarly doesn't mean it's not defined in the spec.

I was just providing further background about whether throwing TypeError causes
an exception or not when attempting to write a readonly data property. In
particular, the JS must be running in strict mode to see this exception.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 23 April 2013 20:37:09 UTC