On Fri, Apr 15, 2011 at 08:38, John J Barton <[email protected]>wrote:
> That sounds like issue 4289 > http://code.google.com/p/fbug/issues/detail?id=4289 > > We have tracked this problem back to a change made in Firefox 4.0. > Firefox team will not revert the change and the fix being proposed > will not be available until Firefox 5.0. > > As far as I am aware there is no practical workaround within Firebug. > > We are investigating whether a workaround can be put into dojo. The > problem is that dojo calls |window.eval()| rather than |eval()| and > Firefox changed the way |window.eval()| works. > may I know what's the suggested workaround we can put into dojo? this problem also seems to prevent break point (or debugger) from working. whenever firebug hits a debugger, I got this in console: Resuming debugger: error during debugging loop: TypeError: firstViewRangeElement is null and I can not debug any dojo based app at all thanks, liucougar -- Frontend Lead, teampatent.com 生于忧患，死于安乐 "People's characters are strengthened through struggle against difficulties; they are weakened by comfort." - Old Chinese adage -- 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.
