Loading Profile...
As noted by another user here:
https://addons.mozilla.org/en-US/fire...
the version 1.4 add-on doesn't seem to work with Firefox 3.6. No buttons appear on supported sites, and the Camelizer toolbar button does nothing when clicked.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
price tracking add-on for Mozilla Firefox does not work
-
I'm using FF 3.6.12 and it works fine, but I will investigate later versions and see what the deal is.
Thanks for letting me know about this.Comment -
-
FF 3.6.13 and Camelizer 1.4 work fine for me.
Tom, could you please provide any other details that might be relevant? Other installed extensions, OS, etc. -
-
The extension used to work, but hasn't - or at least hasn't had any visible UI - for at least several months.
FF 3.6.13 on Ubuntu 9.10 with a pile of other extensions.
I also typically have dozens of windows and hundreds of tabs open.
I restarted the browser and reloaded only one window from my prior session with just a few tabs open to Amazon and NewEgg. I still don't see any buttons within the page (I though there were), but both the toolbar and status bar Camel buttons work as expected (pop-up a graph) with both retailers.
So I guess something from another tab must be interfering. Before I restarted I did take a look at the error console, but it was being flooded with errors from something else. I'll have to track down and eliminate the offending tab first before I can try again with a full session loaded to see if the Camel code throws any errors.-
I believe that the Camelizer is conflicting with (or vice versa) another extension. It will be difficult to remember or look up but do you recall which extensions you installed around the time that the Camelizer stopped working?
-
-
-
-
-
I don't use the Camelizer extension often enough to know when it ceased working, and even if I did, I haven't made any explicit changes to my extension lineup in the past few months, but that doesn't preclude an automatic update from introducing a conflict.
The best hope is that something will show up in the error console that will shed some light.
I've installed NoScript to cut down on the extraneous noise from badly behaved sites, and next I'm going to reload a session with 140 tabs to see if the problem is still reproducible. -
-
The Camelizer extension is working fine with 140 tabs reloaded and NoScript running, though the browser itself seems to be hanging briefly every 5 seconds or so. Something NoScript related.
When the Camel button is clicked while at Amazon, the following errors are logged:
Warning: reference to undefined property event[expando]
Source File: http://z-ecx.images-amazon.com/images...
Line: 642
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
And then when clicked again, another batch:
Warning: reference to undefined property event[expando]
Source File: http://z-ecx.images-amazon.com/images...
Line: 642
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
Warning: reference to undefined property event.target.nodeType
Source File: http://z-ecx.images-amazon.com/images...
Line: 658
which look about the same.
Then at other times not in response to any specific action, I've seen a few of these:
Error: document.getElementById("context-camelizer") is null
Source File: chrome://camelizer/content/ff-overlay.js
Line: 8 -
-
Odd! Does turning NoScript back off break the Camelizer again?
-
-
> Does turning NoScript back off break the Camelizer again?
Apparently not. It's still working. I'll monitor to see if it breaks as the session "ages."
But something to consider is that I was operating under the assumption that the extension added a button to the page UI. I had a recollection that a button near the "add to cart" button - at least for Amazon - was added by the Camelizer extension. And it was the lack of said button that made me think the extension was broken. But now I'm wondering if I was mistaken in that recollection, as I don't see any such button, even though the toolbar and status bar buttons are functioning.
I can't say I recall seeing the status bar button either, when things were not functioning. That's what led me to look up the documentation on the Camelizer and add the toolbar button, which at that time did nothing, so I guess something was definitely broken. -
-
Last year Amazon decided that they didn't like how our extension used to work -- adding a button into the Amazon product page itself -- and made us change it. So now it exists as a toolbar or status bar button.
We mentioned this in a couple of places, such as our blog and the extension pages, but it took quite a while for the Features page to get brought up to date. I apologize for any confusion caused by that.
Please let me know if the problem comes back. -
EMPLOYEE
