Fix issues with feed detection Query the feed probe content script for available feeds from the background script instead of making the content script message the background script. This solves a race condition between the message from the content script sending any feeds associated with the current document and the tab's status "complete" event signaling that a new document has been loaded and hiding the page action. Sometimes that event would be triggered after the message from the content script and thus hide the page action again. In addition, navigating back to a previously visited page might not cause a reload which means that the content script would not send a message if there were feeds associated with the current document.

--- a/manifest.json.in	Wed Sep 18 13:07:06 2019 +0200
+++ b/manifest.json.in	Thu Sep 26 23:11:18 2019 +0200
@@ -30,7 +30,8 @@
     "content_scripts": [
         {
             "matches": [ "http://*/*", "https://*/*", "file:///*" ],
-            "js": [ "content_scripts/feed-probe.js" ]
+            "js": [ "content_scripts/feed-probe.js" ],
+            "run_at": "document_end"
         }
     ],
     "web_accessible_resources": [