I can confirm this also happens with 0.2pre8 and both FF 3.1b2 and 3.2a1pre.
On Jan 11, 4:43 am, Alberto Santini <[email protected]> wrote: > On Jan 8, 5:43 pm, pvncad <[email protected]> wrote: > > > I too observed this with Ubiquity 0.2pre4 beta release on FF 3.0.5 on > > Windows. > > http://labs.toolness.com/trac/ticket/467 > It has been resolved with 0.2pre5. > > > > > I tried to debug with FireBug, I couldn't figure out how to break > > point on ubiquity init code. Could someone let me know > > how one can debug this part of ubiquity code ? > > I opened a post wth title > ChromBug.http://groups.google.com/group/ubiquity-firefox/browse_thread/thread/... > > Regards, > Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" 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/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
