# Unable to debug content scripts

**URL:** <https://discourse.mozilla.org/t/unable-to-debug-content-scripts/72751>\
**Category:** Add-on Support\
**Created:** [December 25, 2020, 9:06pm UTC](https://discourse.mozilla.org/t/unable-to-debug-content-scripts/72751 "2020-12-25T21:06:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeenuv](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/jeenuv/32/23220_2.png) [@jeenuv](https://discourse.mozilla.org/u/jeenuv)\
**Post date:** [December 25, 2020, 9:06pm UTC](https://discourse.mozilla.org/t/unable-to-debug-content-scripts/72751/1 "2020-12-25T21:06:28Z")

</div>

It’s been a while since I had to debug a content script. With 84.0.1, I’m a bit baffled that the debugger doesn’t show script source belonging to any of my extensions (I’ve a handful of them enabled and functional). I can only see sources from the page itself, but nothing from extensions. The debugger window doesn’t show any moz-extension on the left hand side, unlike shown here: [https://extensionworkshop.com/documentation/develop/debugging/#debugging-content-scripts](https://extensionworkshop.com/documentation/develop/debugging/#debugging-content-scripts).

Did anything change recently? Am I missing some other toggle to enable debugging content scripts?

FWIW, I am able to view and debug background page’s sources from about:debugging#/runtime/this-firefox.

---

<div class="post-metadata">

**Author:** ![jeenuv](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/jeenuv/32/23220_2.png) [@jeenuv](https://discourse.mozilla.org/u/jeenuv)\
**Post date:** [December 26, 2020, 9:06am UTC](https://discourse.mozilla.org/t/unable-to-debug-content-scripts/72751/2 "2020-12-26T09:06:02Z")

</div>

OK, I found that there’s “Enable browser chrome and add-on debugging toolboxes” checkbox in the settings for dev tools. Either it’s a new setting, or I lost that when I deleted my old profile and created a new one.

Sorted now.