Given that its in the sandbox, then it's something in one of your subscribed commands. Although I have no idea why context wouldn't be defined in there, unless its to do with bug #237.
Is it happening when you open Ubiquity? When you type anything specific? on page load? Unfortunately, there's no easy way to debug errors like that in 0.1.2 (its being fixed at the moment). So the best way is just trial and error, removing commands until the errors disapears (or starting from scratch and adding them until the error occurs again). - Blair On 31/10/2008 9:29 AM, Derek Featherstone wrote: > On Thu, Oct 30, 2008 at 4:04 PM,<[EMAIL PROTECTED]> wrote: >> you may want to look into FFs error console (Tools>> Error Console) for >> more details (even a call stack) > > Ah, thanks. That does help. Here's what I see: > > =========== > Error: context is not defined > Source File: chrome://ubiquity/content/sandboxfactory.js > Line: 568 > > Error: Traceback for last exception: > getWindow()@chrome://ubiquity/content/sandboxfactory.js:568 > @chrome://ubiquity/content/sandboxfactory.js:1836 > > Source File: chrome://ubiquity/content/msgservice.js > Line: 78 > =========== > > Any ideas? Is this a "reinstall ubiquity" type thing? > > Cheers, > Derek. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
