I've noticed that there's a workaround, but it worked as described by me in all previous versions of Firebug I used. I test my scripts like that pretty often - change a function and check if it works fine (before I publish it).
On Jan 10, 7:05 pm, John J Barton <[email protected]> wrote: > Using your test page I put > window.test = function(){alert('hiya');} > in the console and the alert was > hiya > > The command line is running as if you put > { > command line code} > > into the window. So > test = function(){alert('hiya');} > creates a temporary local property not a property of window. > > jjb > > On Jan 10, 5:35 am, Nux <[email protected]> wrote: > > > Steps to reproduce: > > 1. Create a page with a function call (eg. href with js:...) > > 2. Open FB console > > 3. Write the function (called in 1) differently > > 4. Run script in FB console > > 5. Call the function > > > Actual result: Call of original version of the function > > Expected result: Call of new version of the function > > > My FF: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.0.5) Gecko/ > > 2008120122 Firefox/3.0.5 > > FB: 1.3.0 > > > I've tested this on a very simple web page containing only one (js) > > link and one script that defines the function. You can view it > > here:http://nux.w.of.pl/download/fb_test.html > > In step 3 I 've simply pasted the function definition and changed text > > of the alert message. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
