New issue
Advanced search Search tips

Issue 864953 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 19
Cc:
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevTools now appear to not recognise xhr.send as native code, causing UX issues with blackboxing

Reported by sdodi...@ecomundo.eu, Jul 18 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Steps to reproduce the problem:
1. Create a new XMLHttpRequest(), call its send function
2. Go to the network tab of DevTools, notice the anonymous function
3. Examine the call stack of the XHR request, and notice that xhr.send is an anonymous function instead of built-in code

What is the expected behavior?
The XHR request's send function should show up as native code, so it does not appear as an anonymous, non-blackboxable function, in the call stack of network requests.

What went wrong?
It appears that XMLHttpRequest is no longer considered native code?

Did this work before? Yes 66

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 4.17.3-1-ARCH x86_64
Flash Version: 

Nice bug report template.
chrome-66.png
458 KB View Download
chrome-67.png
396 KB View Download
chrome-66-net.png
453 KB View Download
chrome-67-net.png
499 KB View Download

Comment 1 by viswa.karala@chromium.org, Jul 18

Labels: Needs-Bisect Needs-Triage-M67

Comment 2 by susan.boorgula@chromium.org, Jul 19

Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Feedback
sdodierl@ Thanks for the issue.

Request you to provide a sample file where this issue can be reproduced, which will help in further triaging of the issue.

Thanks..

Comment 3 by sdodi...@ecomundo.eu, Jul 19 

Susan,

My apologies, as I was making a test account for you to test directly on our server, I noticed that I could not reproduce the issue when in Private Mode.

I nailed it down to the LastPass extension intercepting my XHR async=true requests, for some reason.

So, the initial bug report is false.

However, can it be a feature request to say that extensions should be blackboxable? Or is it considered a bug by Google that extensions' code appear in the call stack of the Network tab in DevTools?

Thanks.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 19

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ricea@chromium.org, Jul 19

Status: WontFix (was: Unconfirmed)
If you let an extension inject code into your page, it can do whatever it wants, including making debugging annoying. This is an unavoidable consequence of providing the functionality, and not something we could fix.
►

Sign in to add a comment