Bug 114036 – JSC: Different behaviours when changing value of a readonly properties in a global object.

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: JavaScriptCore

[Stephane Cerveau]

Created attachment 196635 [details]
sample html test

Changing the value of a property's object such as width in window.screen is different in a function than in the main.
ie.
for( var prop in window.screen) {
window.screen[prop] =  0xABADCAFE;
}


In the main, the property value does not change if we assigned a new value but then using this object in a function, the property has been changed.
Please see attached example, index.html.

The bug can be reproduced with Safari 5.1.7 but not with Chromium.

[Stephane Cerveau]

Created attachment 196636 [details]
sample html test with log in document

[Arunprasad Rajkumar]

screen object's properties are readonly.

Refer Screen.idl !

Why you are trying to change that?

[Chris Dumez]

(In reply to comment #2)
> screen object's properties are readonly.
> 
> Refer Screen.idl !
> 
> Why you are trying to change that?

Right, they are readonly so you shouldn't be able to change them, thus the bug :)

I am however unable to reproduce with the test case given and the EFL port (also using JSC).

[Arunprasad Rajkumar]

I tried in Qt Port, it is not changing.

(If possible check the same in Slim Boat, it uses Qt WebKit)

[Benjamin Poulain]

The test case does not return anything wrong on OS X. Closing.

[Stephane Cerveau]

*** This bug has been marked as a duplicate of bug 113831 ***