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

Issue 636070 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Email to this user bounced
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

"Uncaught TypeError: view.isVisible is not a function", source: chrome://net-internals/index.js (984)

Reported by mfor...@gmail.com, Aug 9 2016

Issue description

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

Steps to reproduce the problem:
1. Start chromium from console
2. Start capture from chrome://net-internals/#capture
3. Stop capture, got to export and write a description then choose "Save to file"

What is the expected behavior?
 A file is saved

What went wrong?
 In the console I can see the message:

"Uncaught TypeError: view.isVisible is not a function", source: chrome://net-internals/index.js (984)

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0
 
Labels: Needs-Bisect
Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Able to reproduce the issue on stable 52.0.2743.116 and Beta 53.0.2785.46 - Error message displayed in console

Please find the screenshot

Issue is not reproducible in dev channel 54.0.2824.0 and 54.0.2825.0

Seems the issue got fixed in later versions. Could you please recheck in latest builds and update the thread.
Screenshot from 2016-08-10 15:03:12.png
92.6 KB View Download

Comment 3 by l...@chromium.org, Aug 15 2016

Components: -Platform>DevTools Internals>Network
Labels: -Needs-Feedback -Needs-Bisect
Owner: rchlodni...@opera.com
Status: Fixed (was: Unconfirmed)
Bisected down to:
https://chromium.googlesource.com/chromium/src/+log/1f909cea4097418ded818d7090b77c8abdeb440b..dc50caf6b42799a0f3a532872750a09ac4dacc6e

Seems like this has already been fixed by rchlodnicki@.

Comment 4 by mfor...@gmail.com, Aug 15 2016

 I can confirm that it does indeed work on 54.0.2824.0.
 The problem is that I wanted to report on issue on the stable version and attach the logs but was unable to do so because of this issue.

 Maybe there should be a unit test for this so that it won't break in the future as it's a pretty important feature that people need to submit new issues.

 Thanks.

Sign in to add a comment