On Mar 9, 9:02 am, mechastorm <[email protected]> wrote: > Yeap thats the suggestion that we have given to Facebook. This is > because that is part is code is controlled by Fb themselves. We > developers basically load up our app within Fb's own app. > > I'm not sure why they suddenly decided to like override the console > var. Just happened over the weekend it seems.
My guess is that they did not 'decide'. Rather my guess is that they started to use someone else's code for some part of the production site and did not factor in that external devs may use the production site with Firebug. jjb > > On Mar 9, 4:17 pm, John J Barton <[email protected]> wrote: > > > On Mar 9, 3:14 am, mechastorm <[email protected]> wrote: > > > > Just FYI for those Facebook Developers who debug Facebook via Firebug. > > > > Facebook has essentially broken the use of Firebug recently. None of > > > the apps/games that use JS will run when Firebug is enabled > > > (specifically the JS console). Disabling the firebug console allows it > > > to work again. > > > >http://bugs.developers.facebook.com/show_bug.cgi?id=9131 > > > > It is really annoying since now its impossible to do any debugging > > > work. I have switched to Opera's DragonFly for now but the interface > > > is not as straightforward as Firebugs and you don't get console.debug > > > in Opera I think. > > > Well the script fromhttp://static.ak.fbcdn.net/rsrc.php > > tries to re-assign the console object: > > [Break on this error] function muffinize(d){var c='a';var b=... > > console=console||{log:bagofholding}; > > > If you implement this as: > > if (!console) console = {log:bagofholding}; > > then you won't get the error message. > > > jjb > > > > Anyways it's just a heads up. -- 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.
