Skip to content

[Bug]: Complexity 2.9.18 works in Comet on Windows 11 but not in Chrome 147 (toggles inactive) #165

@DimaTre

Description

@DimaTre

Version

2.9.18

Browser

Chrome 147.0.7727.138 (Official build) (64‑bit)

Describe the bug

Hi,

First of all, thanks for the awesome extension — it works great in the Comet browser.

However, I’m seeing a strange issue where Complexity works fine in Comet, but not in Google Chrome on the same machine.

Environment

  • OS: Windows 11
  • Browsers:
    • Comet (Chromium‑based) — Complexity v2.9.18
    • Google Chrome 147.0.7727.138 (Official build) (64‑bit)
  • Extension version: Complexity v2.9.18 (from Chrome Web Store)

What happens

  • In Comet: the extension activates on https://www.perplexity.ai and the features work as expected.
  • In Chrome:
    • The extension is installed and enabled in chrome://extensions.
    • I open a regular tab with https://www.perplexity.ai (not a PWA window).
    • The Complexity settings page shows all the feature toggles in a “dimmed” / inactive‑looking state.
    • Toggling features there does not seem to have any effect on the Perplexity tab.
    • On the Perplexity tab itself, no Complexity UI appears and there is no visible reaction from the extension.

What I’ve already tried

  • Disabled all other extensions.
  • Created a fresh Chrome profile and installed only Complexity 2.9.18.
  • Removed and re‑installed the extension from the Chrome Web Store.
  • Confirmed that Perplexity is opened in a normal tab and that the site itself works (I can use Perplexity normally).

The behaviour is always the same: Complexity works in Comet, but in Chrome the switches in the plugin UI look active/inactive visually, while nothing happens on perplexity.ai.

DevTools console

When I open DevTools → Console on https://www.perplexity.ai in Chrome, I only see Perplexity’s own network/CORS errors (404 / ERR_FAILED from their CDN). I do not see any errors or logs that appear to come from Complexity when I toggle features in the extension UI. This looks like the content script never attaches to the Perplexity tab in Chrome.

Question

Is this a known issue with Chrome 147 or with the current Perplexity / Comet changes?
Any guidance, workaround or debug build that could help understand why the content script doesn’t attach in Chrome would be greatly appreciated.

Thanks in advance!

Dima

Bug confirmation

  • I am not able to reproduce the issue with the extension disabled
  • I have re-installed the extension and the issue persists

Steps to reproduce

See

Expected behavior

Same Comet

Debug Logs

a

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions