Recensioni per ChromeLogger
ChromeLogger di BurningMoth
Recensione di Utente Firefox 13079274
Valutata 5 su 5
di Utente Firefox 13079274, 8 anni fa28 recensioni
- Valutata 5 su 5di AmericanIntelligenceMachines, un anno fa
- Valutata 5 su 5di Utente Firefox 17447093, 4 anni fa
- Valutata 5 su 5di Utente Firefox 16987925, 5 anni fa
- Valutata 4 su 5di Utente Firefox 15307722, 6 anni fa
- Valutata 5 su 5di Utente Firefox 15064500, 7 anni fa
- Valutata 5 su 5di Utente Firefox 14666722, 7 anni fa
- Valutata 5 su 5di Utente Firefox 14035565, 8 anni fa
- Valutata 5 su 5di Joe Rooster, 8 anni faWorks as expected and better than other add-ons that (try to) put out messages from ChromePHP. Thank you :-)
- Valutata 5 su 5di Utente Firefox 13483795, 8 anni faOk so the problems I reported earlier are fixed and logging is working as expected now. Thanks for a great bit of digital kit?
- Valutata 5 su 5di Patrick Brosset, 8 anni faWorks for me now. It was updated last week and it fixes the issue people have been talking about in the comments!
Thanks! - Valutata 5 su 5di Utente Firefox 13328225, 8 anni faSince version 1.1.1 it works as it should. Thanks!
- Valutata 4 su 5di Utente Firefox 13518149, 8 anni fa
- Updated 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.