You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[MERGE #6135@boingoing] SetProperty doesn't handle the case where the receiver object has a non-writable property
Merge pull request #6135 from boingoing:nonwritablepropertyreceiver
SetProperty doesn't handle the case where the receiver object has a non-writable property
When checking for non-writable properties while trying to set a property, we only check the object. If the receiver has a non-writable property we should throw in strict mode.
Also adds StSuperFldStrict and a profiled version because strictness is not preserved in some backend calls to StSuperFld.
Fixes: #5948
0 commit comments