New issue
Advanced search Search tips

Issue 759622 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Can't click on HTML elements inside inspector

Reported by i...@robsmittenaar.com, Aug 28 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. Open inspect element
2. Click on HTML elements (open / close elements / change css values).
3. After a short amount of time it appears to freeze. Although I can still click within the dev tools it does not respond accurate.

What is the expected behavior?
Open close HTML elements in inspector, change css values etc.

What went wrong?
Can't edit / select any code and appears to freeze.

Did this work before? Yes Not sure, since 2 weeks as of now.

Chrome version: 60.0.3112.113  Channel: stable
OS Version: OS X 10.12.3
Flash Version: 

Tested in Chrome, Incognito and Canary. Dit a reset of all preferences, created a new user, tested on multiple computers, same bug.
 
chrome-bug.mp4
3.2 MB View Download
Labels: Needs-Triage-M60
Can't repro this :( Is this clean profile?
Yes, created a new profile, removed all extensions, installed beta, canary / latest stable release. Experienced it on multiple iMac / Mac Mini systems (4 in total) so definitely not something related to one single setup. All systems are using a Wacom, could this be related to the problem?
Here is what I would ask you to do:

- Get a clean profile so that you had no personal info / cookies / login info there.
- Get to the state when it gets slow / freezes
- Open a new tab, point to about:tracing
- Select Record -> Web Developer -> Record
- Go back to the frozen page, perform some actions that should get feedback
- Turn back to about:tracing and stop recording
- "Save" trace, attach it here.
trace_chrome_bug.json.gz
4.5 MB Download
chrome_bug.mp4
7.7 MB View Download
Thanks! Can't see anything stalling in the trace, so it means the system is responsive, just does not work properly. Chrome 61 is going to be released early next week, let's see if it still reproes there.

Also, could you undock devtools and hit Cmd+Option+I to open devtools for that devtools and see if console has any errors?

Comment 8 by alph@chromium.org, Oct 10 2017

Labels: Needs-Feedback

Comment 9 by alph@chromium.org, Oct 16 2017

Status: WontFix (was: Unconfirmed)
Closing as non reproducible.

Sign in to add a comment