> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/chrome-extension-pull-request/report-chrome-extension-issues.md).

# Report Chrome Extension Issues

### Overview <a href="#overview" id="overview"></a>

* Extension bugs are more difficult to troubleshoot comparing to the web app (aka dashboard). This is due to the fact that the extension is running in a “foreign” playground - the user’s environment - while the web app is running in its own playground
* We may not be able to reproduce scenarios in an accurate fashion because the users often work in their secure environment, which may not be available to us
* The extension lives in 3 different “zones”:
  * Popup - appears when clicking on the extension icon
  * Content - the metrics overlay and the manual test widget
  * Service worker (Background) - the data flowing between the extension and SL BE
* The **content** lives inside the host page, meaning it can impact anything inside the page (and conversely, the page can affect the extension’s appearance and behavior)
* The extension communicates with our BE only thru the service worker (background)

### Identify the installed version <a href="#identify-the-installed-version" id="identify-the-installed-version"></a>

* Find it in the extensions page (**chrome://extensions/**). Below it shows that version 1.11.7 is installed

  <figure><img src="/files/KsmpUlpACtxW97yrN2zl" alt=""><figcaption><p>Extension version in the browser’s extensions page</p></figcaption></figure>
* You can also check the installed version when clicking on the extension icon from the browser’s toolbar:

  <figure><img src="/files/LkvfPHEEP87BSJ7eVKVu" alt=""><figcaption><p>Extension version appears in its menu</p></figcaption></figure>
* Verify that the latest extension version is installed

### Open the windows where the extension related data is visible <a href="#open-the-windows-where-the-extension-related-data-is-visible" id="open-the-windows-where-the-extension-related-data-is-visible"></a>

* Open the browser’s **Developer Tools** of the page hosting the extension. It is either
  * The SCM page where the extension shows metrics overlay (e.g. Pull Request)
  * The page where the user is running a manual test

    <figure><img src="/files/AZ9Ll5t3wz0MK9qQURWI" alt=""><figcaption><p>Developer tools menu item (in Chrome for Windows)</p></figcaption></figure>
* In the extensions page (**chrome://extensions/**) switch on **Developer mode** (located in the top right corner of the page)

  <figure><img src="/files/LNmDpSM7NKHgDB1fQcSZ" alt=""><figcaption><p>Switching on Developer mode</p></figcaption></figure>
* click the **service worker** link found in the extension box

  <figure><img src="/files/xBBNQRJQCCn8DpFnTHQY" alt=""><figcaption><p>Link to the extension’s service worker</p></figcaption></figure>

### Collect helpful data <a href="#collect-helpful-data" id="collect-helpful-data"></a>

* The **Console** tab of the host page **Developer Tools** may contain helpful data. Especially when there is an error

  <figure><img src="/files/qwA52OYZn3mH0cMUnnjr" alt=""><figcaption><p>The <strong>Console</strong> tab of the <strong>Developer Tools</strong></p></figcaption></figure>
* The Network tab of the service worker.Select the **Fetch/XHR** list as illustrated below

  <figure><img src="/files/kL3sZqQ5Az7uTgHeX4lz" alt=""><figcaption><p>The <strong>Network</strong> tab of the extension’s service worker</p></figcaption></figure>
* Right clicking on any request in the list will show the following menu where the user can copy anything related to the selected request and send it to us for further investigation. Provide us with the content of both options **Copy link address** and **Copy response**.

  <figure><img src="/files/LebCeX3LBrJwZQUVjAl1" alt=""><figcaption><p>Network resource menu</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/chrome-extension-pull-request/report-chrome-extension-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.