Reviews for ChromeLogger
ChromeLogger by BurningMoth
Review by phillipmiller
27 reviews
- Rated 5 out of 5by DP Dev, a year ago
- Rated 5 out of 5by Nina, a year ago
- Rated 5 out of 5by Firefox user 17447093, 3 years ago
- Rated 5 out of 5by Firefox user 16987925, 3 years ago
- Rated 5 out of 5by iNeRdS, 4 years agoi need you to monitor all my activities from this I.P. address I am sure you boys no what to do better than i describe
- Rated 5 out of 5by Don, 5 years ago
- Rated 4 out of 5by Firefox user 15307722, 5 years ago
- Rated 5 out of 5by Firefox user 15064500, 5 years ago
- Rated 5 out of 5by Firefox user 14666722, 6 years ago
- Rated 5 out of 5by Firefox user 13079274, 6 years ago
- Rated 5 out of 5by Firefox user 14035565, 6 years ago
- Rated 5 out of 5by dadazord, 7 years ago
- Rated 5 out of 5by Joe Rooster, 7 years agoWorks as expected and better than other add-ons that (try to) put out messages from ChromePHP. Thank you :-)
- Rated 5 out of 5by Firefox user 13483795, 7 years agoOk so the problems I reported earlier are fixed and logging is working as expected now. Thanks for a great bit of digital kit?
- Rated 5 out of 5by Patrick Brosset, 7 years agoWorks for me now. It was updated last week and it fixes the issue people have been talking about in the comments!
Thanks! - Rated 5 out of 5by Firefox user 13328225, 7 years agoSince version 1.1.1 it works as it should. Thanks!
- Rated 4 out of 5by Firefox user 13518149, 7 years ago
- Rated 5 out of 5by skrymir01, 7 years agoUpdated Review:
Issue's been resolved and logs my messages like a champ.
Previous Review:
Produces error: TypeError: window.console[method] is undefined
The reason appears to be that it assumes the console method will be sent in the response. This will be the case for the all logging types _except_ "log". According to the Chrome Logger technical specifications at https://craig.is/writing/chrome-logger/techspecs, if you want to log, you should send an empty string (to save on size). Therefore the add-on ought to use "log" if "method" is empty. I believe the following would be sufficient to fix it:
console[method || 'log']
I couldn't find a repository to log this issue at or submit a pull request, so I had to use the review section. - Rated 4 out of 5by Firefox user 13497262, 7 years agoIt works great after the workaround with chrome-logger.