- Sep 4, 2006
- 16,800
- 45
- 91
Alright, there's this problem I'm having. I have a popular google chrome extension that I've developed. However, it keeps breaking for a variety of users over time. This isn't the end of the world or anything but it is annoying. And, sometimes, it breaks in mysterious ways.
Now, the thing that I'd like to do is add more console.logs and try/catch clauses and so forth but that's all kinda pointless if I can't get the user to report the problem back to me. The extension is for a particular website that uses a lot of dynamic code. I could report the issue in the dev tools console but that's useless for my casual users because they don't know how to bring that up and report back and yadda yadda. Too much work!
I need a better way for them to report the problem that's occurring with some information along with it. Is there a viable way to go about this? I thought of having some kind of ultimate catch function that catches all errors and console.log messages that my extension put out (logging them in some variable) and then pushes them out into the page into a handy link where the user can report the problem by clicking the link. (It'd automatically submit a report and so forth) However, there's not a good way to go about that (particularly in the sense of what service do I use for the link? I'd consider using my personal website if I could setup some root@mywebsite.com email account and some php page that fired off an email to my trident@gmail.com email address with all the info...)
Now, the thing that I'd like to do is add more console.logs and try/catch clauses and so forth but that's all kinda pointless if I can't get the user to report the problem back to me. The extension is for a particular website that uses a lot of dynamic code. I could report the issue in the dev tools console but that's useless for my casual users because they don't know how to bring that up and report back and yadda yadda. Too much work!
I need a better way for them to report the problem that's occurring with some information along with it. Is there a viable way to go about this? I thought of having some kind of ultimate catch function that catches all errors and console.log messages that my extension put out (logging them in some variable) and then pushes them out into the page into a handy link where the user can report the problem by clicking the link. (It'd automatically submit a report and so forth) However, there's not a good way to go about that (particularly in the sense of what service do I use for the link? I'd consider using my personal website if I could setup some root@mywebsite.com email account and some php page that fired off an email to my trident@gmail.com email address with all the info...)