New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 628948 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android
Pri: 2
Type: Bug



Sign in to add a comment

Inspect device: console output and errors randomly appear before "Navigated To"

Reported by teo8...@gmail.com, Jul 17 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Connect an android device to the computer & enable USB debugging
2. On the computer, inspect device
3. On the device, open a page that produces output to the console and/or triggers errors

What is the expected behavior?
All the output and the error should show up *after* the "Navigated to ..." message

What went wrong?
At random times, it starts happening that all the output and errors appear systematically before the "Navigated to" message. If you reload the page or navigate from a page to another, this generate huge confusion and makes debugging a f***ing hell 

Did this work before? Yes I don't know, I've started observing this recently

Chrome version: 51.0.2704.106  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0

I'm pretty sure I had experienced this issue ages ago, probably NOT inspecting device but on Desktop Chrome, and it must have been fixed because I hadn't seen this for ages.
Now I'm observing this again, but only when inspecting mobile devices. Unless it's totally random.

Either way, it's f***ing pathetic
 

Comment 1 by caseq@chromium.org, Jul 18 2016

Cc: lushnikov@chromium.org
Labels: OS-Android
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: dgozman@chromium.org
Owner: l...@chromium.org
I see where this comes from - we add "Navigated to" messages after navigation has completed. If you log before that, the order is messed up.

Comment 3 by l...@chromium.org, Jul 22 2016

It looks like this bug also occurs when debugging normally (without remote device).

Comment 4 by l...@chromium.org, Dec 2 2016

Labels: Hotlist-Polish
Owner: kozyatinskiy@chromium.org
Status: Started (was: Assigned)
Labels: -Hotlist-Polish
Status: Assigned (was: Started)
Owner: kozy@chromium.org

Comment 8 by teo8...@gmail.com, Nov 1 2017

For fuck's sake, more than a year later this is still unfixed !?!?

Comment 9 by kozy@chromium.org, Jan 3 2018

Status: WontFix (was: Assigned)
I believe that it is fixed in latest Canary. Feel free to reopen this one if it still an issue.

Sign in to add a comment