Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cs.js produces "getElementById(...) is null" on all pages #18

Open
Xirema opened this issue Oct 24, 2024 · 1 comment
Open

cs.js produces "getElementById(...) is null" on all pages #18

Xirema opened this issue Oct 24, 2024 · 1 comment

Comments

@Xirema
Copy link

Xirema commented Oct 24, 2024

Mostly the error seems to be benign, but I've had at least one case (strangely enough the gateway web app of my modem) where this error causes the page to render incorrectly, so I've had to disable the addon.

This error gets spammed in the console for all web pages:

TypeError: document.getElementById(...) is null[cs.js:136:10](moz-extension://f2061c24-b8f6-4db7-b9bb-1db0386f7a6e/cs.js)
    <anonymous> moz-extension://f2061c24-b8f6-4db7-b9bb-1db0386f7a6e/cs.js:136
    #injectIntoIsolatedWorld resource://gre/modules/ExtensionContent.sys.mjs:678
    inject resource://gre/modules/ExtensionContent.sys.mjs:663
    injectInto resource://gre/modules/ExtensionContent.sys.mjs:534
    AsyncFunctionNext self-hosted:807
@maxstarkenburg
Copy link

As noted in #20, this error seems to break DuckDuckGo from displaying results. I'm guessing that all those document.getElementById added in afa9522 may need better error handling, not just the one on line 136.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants