Workaround for Chrome not specifying which request is main_frame under some circumstances

webrequest.js

Index: webrequest.js
===================================================================
--- a/webrequest.js
+++ b/webrequest.js
@@ -56,6 +56,13 @@
     return {};
 
   var type = details.type;
+  
+  // Workaround: Under some circumstances Chrome 29+ gives top frame the
+  // type "object" instead of "main_frame". We work around that by assuming
+  // that the first request belongs to the top frame.
+  if (!(details.tabId in frames))
+    type = "main_frame";

[Wladimir Palant, 2013/08/29 05:57:40]

There are two assumption here which both seem to be wrong:

1) This issue will always manifest itself as an unknown tab ID. I doubt that
this is the case - if the user navigates to that YouTube URL in an existing tab
then the tab will be known.

2) A request initiated from an unknown tab is always this issue. However, we
will only get the top request if it comes from HTTP or HTTPS. A local file
making requests to remote resources will show up as an unknown tab. Also, some
requests (like requests made by extensions) aren't associated with tabs - tabId
will be -1 then.

+  
   if (type == "main_frame" || type == "sub_frame")
     recordFrame(details.tabId, details.frameId, details.parentFrameId, details.url);