Oleg Shevchenko

I know that the response is very late, but anyway. We are going to completely redesign the popup, WIP is here: https://github.com/olsh/Feedly-Notifier/tree/redesign

Well, I'm not sure if we want to implement this feature, because there are other extensions on the store with this functionality. For instance: https://chrome.google.com/webstore/detail/feedly-mini/ndhinffkekpekljifjkkkkkhopnjodja?hl=en https://chrome.google.com/webstore/detail/feedly-subscribe-button/gbbnddjfcllebfcnihfgmdplgaiejepc?hl=en

Yes, the feature was in the old FF version. https://github.com/olsh/Feedly-Notifier-Firefox But now we are using WebExtensions, so we need to reimplement it. PRs are welcome.

AFAIK, the only way to create an incognito window is the context menu. In order to see the `Open in an incognito window` we should put the href element on...

Hi @AlexNk It seems like FF disposes `feedIds` and the function fails with `can’t access dead object` https://github.com/olsh/Feedly-Notifier/blob/master/src/scripts/core.js#L787 The disposing of objects is a feature https://blog.mozilla.org/addons/2012/09/12/what-does-cant-access-dead-object-mean/ Simple array copying doesn't...

Well, this is not webextension specific bug. The aggressive GC behaves the same for all types of FF add-ons. For now, I don't have a solution for the issue.

Yes, of course, the addon works even if the popup is closed. The problem is that the _`feedIds` is created in the `popup.js`_ and passed to the `core.js` (background page).

Hi @AlexNk , Thanks for the investigation 👍 I used `splice` function for the array copying, and this didn't work. Will try your code.

Could you please specify your browser and OS?

It seems like a Linux only bug. Have you tried to set the option to 3 for example?