The only event that seems to fire for the no content frame is webNavigation.onBeforeNavigate. The events onCommitted, onDOMContentLoaded, and onCompleted never fire. Using the manifest to inject scripts doesn't work because the no content frame is ignored even for <all_urls> and matchAboutBlank = true. For an extension that wants to execute something in all frames, but can wait until later in the load process (for better user experience), this is a difficult situation. 

The issue seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation.

Thanks...!!

Bumping in case this has fallen through cracks ...

Thanks for the bump, it indeed had fallen through. I've managed to repro locally and will investigate, however I will be out of office for a next week, so it won't be immediately.

It looks like with PlzNavigate, we treat 204/205 as an actual error, which means we don't send anything to the renderer process (https://cs.chromium.org/chromium/src/content/browser/frame_host/navigation_request.cc?rcl=4d7a9ea81684ff23d235642fa97f5bbd110911f5&l=642). Inside the webNavigation API implementation, we don't track frames that haven't committed and because of the ERR_ABORTED treatment, the frame is not added to the tracking list, which in turn means we don't add it to the output of getAllFrames. 

Without PlzNavigate, we don't go through the same path as above, however we still get a DidFinishNavigation which has NavigationHandle with HasCommitted and IsErrorPage both set to false, which causes the same skip of adding to the state tracking list.

Adding rdevlin.cronin@ to look at tabs.executeScript, as it doesn't use the same underlying state tracking, so not sure why that one gives us an error.