ChromeLogger 的评价
ChromeLogger 作者: BurningMoth
25 条评价
- 评分 5 / 5来自 远离中共邪教快退出党团队, 10 天前
- 评分 5 / 5来自 退出党团队远离中共邪教, 2 个月前
- 评分 5 / 5来自 AmericanIntelligenceMachines, 2 个月前
- 评分 5 / 5来自 Firefox 用户 17447093, 3 年前
- 评分 5 / 5来自 Firefox 用户 16987925, 4 年前
- 评分 5 / 5来自 Firefox 用户 15064500, 6 年前
- 评分 5 / 5来自 Firefox 用户 14666722, 6 年前
- 评分 5 / 5来自 Firefox 用户 13079274, 7 年前
- 评分 5 / 5来自 Firefox 用户 14035565, 7 年前
- 评分 5 / 5来自 Joe Rooster, 7 年前Works as expected and better than other add-ons that (try to) put out messages from ChromePHP. Thank you :-)
- 评分 5 / 5来自 Firefox 用户 13483795, 7 年前Ok so the problems I reported earlier are fixed and logging is working as expected now. Thanks for a great bit of digital kit?
- 评分 5 / 5来自 Patrick Brosset, 7 年前Works for me now. It was updated last week and it fixes the issue people have been talking about in the comments!
Thanks! - 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.