|
Post by jonphipps on May 6, 2006 9:59:24 GMT -5
After an upgrade to FF 1.5.0.3 and with MenuEditor 1.2 enabled, I get a JS dialog box with the following error one or more times on each rendered page: "TypeError: oContext has no properties"
Firebug then reports that Google Toolbar and the "View Dependencies" extension both generate "menu has no properties" errors.
All of this goes away if I disable MenuEditor, which is a shame because I have come to depend on it to tame my out-of-control menus (I have a lot of extensions).
It's possible that this is a conflict with another extension but I've disabled all of the extensions that I could think of that modify the context menu and then some, but I still get the TypeError message, apparently from MenuEditor(?).
|
|
|
Post by Devon J on May 8, 2006 18:58:46 GMT -5
Hmm, no one has reported this problem before. What happens if only menu editor is enabled?
So these errors are popping up in little windows? not just showing up in the javascript console. Are there errors in the javascript console? (or it that what firebug is reporting?)
You could try wiping out the menu editor settings and starting fresh - Close firefox, delete "menuedit.rdf" from your profile folder, open firefox, enable menu editor, restart firefox.
|
|
|
Post by jonphipps on May 10, 2006 7:33:52 GMT -5
Well, the problem is gone without actually being resolved, 'resolved' in the sense that I know what happened and fixed it. See below for what I did... re: "So these errors are popping up in little windows?" They're JS alert dialogs. re: "Are there errors in the javascript console? (or it that what firebug is reporting?)" That's what FireBug is reporting re: "What happens if only menu editor is enabled?" I didn't go that far, but I messed around with disabling & uninstalling extensions and discovered that there were several extensions that wouldn't uninstall, even in safe mode. This struck me as bad. So I restored my last backup pre-FF1.5.0.3, updated to 0.3, restarted, and then updated one at a time the extensions that had been updated since then, with a FF restart between each. And the problem has not returned. I have no idea what's different. Thanks for your response. I continue to be very happy with Menu Editor. --Jon
|
|