Issue metadata
Sign in to add a comment
|
Network tab does not show gapi calls from background page of chrome extension |
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36
Steps to reproduce the problem:
1. Create a chrome extension that makes calls to gapi in a background script, ex:
var request = gapi.client['yourapi']['yourmethod'].search(resource);
request.execute(function(resp) {
if (!resp || resp['error']) {
callback(null);
} else {
callback(resp);
}
});
2. open the devtools for for the background page of the extension
3. cause the extension to make the call.
3. look at the network tab.
What is the expected behavior?
The network tab should show the call to the API
What went wrong?
Call is not shown in the list of network requests (but request does execute and results are returned)
Did this work before? Yes Not sure. Definitely within lat 6mo
Chrome version: 58.0.3029.96 Channel: n/a
OS Version:
Flash Version: Shockwave Flash 25.0 r0
For google developers, see companion internal bug with an easy example of how to reproduce using one of our internal chrome extensions. b/38233934
,
May 12 2017
@Reporter: Thanks for the issue. could you please provide us any sample html/JS file to triage the issue from TE end. Also please try the issue once on latest stable 58.0.3029.110 and update the thread. Thanks,
,
May 18 2017
Regular fetch and XHRs from an extension's background page still show up. On the surface, it looks like this particular case, the background page sends a postMessage to an iframe, giving it enough info to make a request. If the iframe is making a request, we should be catching it, but I haven't looked into this deep enough. Are you aware of other extensions using gapi that are affected?
,
Jul 5 2017
,
Jul 17 2017
,
Jul 18 2017
I am going to close this bug. It looks like the XHR request was catchable as long as the right target was being inspected. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, May 12 2017