'Failed to download comments' erroneous error

[atomGit]

was troubleshooting why there's no comment count badge on the toolbar icon (likely due to privacy stuff in my config), so i spun up a clean profile, installed comntr and headed to the AMO page where i know there was a comment left - got this...

Failed to download comments: TypeError: NetworkError when attempting to fetch resource.

at the very same time comntr is loading comments from that AMO page on my normal FF profile

[atomGit]

it looks like part of the problem is the url - i just tested this again and the AMO url included the param ?src=search and so comntr doesn't see comments there - if i remove that param, it now sees the comment

still don't know the reason for the network error and i'm not seeing any requests from comntr to the github resource or comntr.live in the FF dev tools network requests

[atomGit]

i tested again with a clean profile and got the same error again - the url i'm testing is... https://addons.mozilla.org/en-US/firefox/addon/comntr/

there are comments there (i left them), but... Failed to download comments: TypeError: NetworkError when attempting to fetch resource.

i don't know why it would fail sometimes and not others with a fresh profile, yet comments are always displayed with my normal profile (but there's no badge count)

update:

was setting up to some more testing and without changing anything (fresh profile) comments were displayed for the given url

i wonder if FF is blocking cmntr and/or its external resources until FF has had a chance to download certain lists, such as the add-on blacklist, blacklisted domains, malware list, etc.?

however the toolbar icon did not show the badge for the number of comments

[comntr]

One similar issue that I've seen on Firefox desktop (Ubuntu), was that Firefox didn't like the LetsEncrypt cert. To check if this is the case, open https://comntr.live:42751 in a new tab.

There is another bug when the extension stops updating the comments count badge. This happens in Chrome dekstop and Firefox Android. When this happens, the dev console in Chrome for that extension is empty. I guess that this is something to do with how background.js is registered. In any case, it's useful to write the last 1 MB of logs to indexedDb and download them on request.

[atomGit]

i've never had a problem with comntr.live when opened directly and my website uses the Let's Encrypt cert which has never caused a problem - also i'm using FF desktop

i don't suppose that helps you any, but there it is :)

if you want me to do any logging or whatever, let me know

[comntr]

If you see this bug often, it makes sense to do this logging sonner. The extension (background.js essentially) needs to forward all logs to a table in indexedDb, but the table should keep only last 100K logs in circular buffer. Then there should be button in the context menu (there already two) that would pull all the logs from that table, zip them and save as a file.