Skip to main content

Why does a function declaration override non-writable properties of the global object?


Setting a property descriptor like this:




Object.defineProperty(window, 'someFunction', {
value: function() { alert('safe'); },
writable: false,
enumerable: false,
configurable: false
});



...should, as far as I know, make the someFunction property of window non-writable. It works for function expressions as I expect, whether the function is directly assigned to the object property... fiddle




window.someFunction = function() { alert('boom!'); }
someFunction(); // safe



...or assigned to a global variable: fiddle




var someFunction = function() { alert('boom!'); }
someFunction(); // safe



However, it doesn't seem to work with function declarations : fiddle




function someFunction() { alert('boom!'); }
someFunction(); // boom!



Is this behavior intentional? What is the reasoning behind it? Is this documented anywhere? Or am I just making some kind of silly mistake?





By the way, I'm using Chromium 17 to test this. Strict mode doesn't seem to make any difference.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. This is a bug (see Bug #115452), which I also encountered when answering this question.

    Compatibility check: Test case


    In Firefox 4+, it works fine.
    In Chrome 16, it works fine.
    In Chrome 17, it does not work.
    IE8- doesn't have Object.defineProperty, so it doesn't work
    In IE9, it does not work.
    In Safari 5, it does not work.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex