afschwartz

For this first pass I went with a markdown-like syntax. However, I'm not tied to it.

Submit a PR here https://github.com/adamschwartz/log/pulls and we'll consider it if there is wide support.

Thanks for these suggestions. You can track progress on this here: https://github.com/adamschwartz/log/issues/1

Just updated the instructions: https://github.com/adamschwartz/log/commit/919f8ffac919f0183...

Basically just open the javascript console.

We agree. We're actively looking into other ways to do the detection. For example, when the inspector is docked, we might not need to run the profiler check. We'll continue to update as we find better solutions.

Starred. Thanks for the submission. Would definitely be better to have this integrated into the browser.

Yup! We credited http://stackoverflow.com/a/15567735/131898 in the README (https://github.com/adamschwartz/chrome-inspector-detector/bl...) which in turn credits you. :)

Perhaps you're making a javascript game and want to pause it or show wireframes when toggling the inspector. Things like that...

It may not be clear, but the main use case for this app is not to harm someone, but to aid in development. Perhaps you're making a game and want to pause it or show wireframes when toggling the inspector. Or perhaps you're a designer and you want to show a grid layout whenever you're inspecting elements.

It may not be clear, but the main use case for this app is not to harm someone, but to aid in development.

Perhaps you're making a game and want to pause it or show wireframes when toggling the inspector.

Or perhaps you're a designer and you want to show a grid layout whenever you're inspecting elements.

Yup! :)

Just updated with OS-specific instructions: https://github.com/adamschwartz/chrome-inspector-detector/co...

@goldfeld absolutely. However, the profiler check mucks up the console output so I was hoping to use it as a fallback. For now I've made it experimental and will keep it that way until we can resolve the issues you pointed out. (https://github.com/adamschwartz/chrome-inspector-detector/is...)

Does that make profiling unusable?

I've made the docked/undocked an experimental feature since it was causing the issues you were seeing. Please let me know if you're still seeing any issues with false positives for open.

Can you provide any other information?

I've made the docked/undocked an experimental feature since it was causing the issues you were seeing. Please let me know if you're still seeing any issues with false positives for open.

Thanks for reporting all of the issues.

I'll continue to improve and update https://github.com/adamschwartz/chrome-inspector-detector/is... with the issues reported here. Thanks.

Thanks for the bug report. The downloads bar bug is fixed.