You have a "debugger;" call in addToFirebase that's making my Firebug angry. I can't seem to make the script panel ignore this line, even with a conditional 1==0 breakpoint.
Would you be able to take the "debugger" calls out of the production code?
edit:
After some more testing, in Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.
After some more testing, in Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.
In Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.
HN was causing problems for me earlier (as seen by by duplicate replies above that I eventually put in as an edit...) but I wanted to say thanks.
Also I wanted to make two suggestions if you're looking for features to build:
1) Highlight "important" annotations in the console in some way.
2) Allow option for submitted notes/screenshots to be forwarded via email both as archive and for searchability etc.
In Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.
In Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.
This seems like a useful service, but I've been burned too many times to start using a service before I know what the pricing will look like. No pricing == no evaluation for me, as a general rule. General assurances that it'll be reasonable/flexible haven't panned out in the past.
Thanks for this. We'll hash something out in the next couple of days. If you want me to follow up, ping me at leo@kivo.com and I'll reach out to you with some more definite info.
Would you be able to take the "debugger" calls out of the production code?
edit: After some more testing, in Chrome I can make it work by just closing the Dev Tools windows, but Firebug gets caught up on it as long as it is enabled, even if not open currently. This means I have to disable Firebug entirely in order to use this on my page. I don't really want to do that, as I am using it in my workflow for otherwise debugging the code I manage.