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

Issue 884754 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 19
Cc:
█ krajshree@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Cannot open developer tools, neither use "inspect element"

Reported by ma.vanbr...@crestec.nl, Sep 17 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Steps to reproduce the problem:
1. Create a new Chrome profile
2. Go to our custom web app (internal URL with plain http)
3. Press F12 to access the developer tools
4. Press CRTL+SHIFT+I to inspect an element
5. Wait a couple of minuter/hours
6. Go back to our web app, and it cannot open the dev tools neither inspect element
7. Going to the https version works, or the http with IP address

What is the expected behavior?
Be able to access the developer tools or inspect element all the time

What went wrong?
I cannot access the developer tool/inspect element

Did this work before? N/A 

Chrome version: 69.0.3497.92  Channel: stable
OS Version: 10.0
Flash Version:

Comment 1 by susan.boorgula@chromium.org, Sep 17

Labels: Needs-Triage-M69

Comment 2 by asch...@republicsd.org, Sep 17 

Is this device a school-issued device or a personal device?

Chrome does have enterprise locked down procedures to remove inspect element abilities entirely if chosen by the administrator of the device.

Comment 3 by ma.vanbr...@crestec.nl, Sep 18 

It is a Windows 10 desktop joined to Active Directory.
I've check the policies, but we are not controlling any of the developer features, neither by AD or G Suite admin.

Comment 4 by ma.vanbr...@crestec.nl, Sep 19 

I've fixed this issue by downloading and updating the latest Chrome MSI policy bundles from: https://enterprise.google.com/chrome/chrome-browser/

I've deleted the old GPO and created a new one from scratch with the updated ADMX files and afterwards the issue has been fixed.

Comment 5 by krajshree@chromium.org, Sep 19

Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
reporter@ - As per comment #4, please let us know if the issue can be closed.

Thanks...!!

Comment 6 by ma.vanbr...@crestec.nl, Sep 19 

Yes, please close it.
Project Member

Comment 7 by sheriffbot@chromium.org, Sep 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 8 by krajshree@chromium.org, Sep 19

Status: WontFix (was: Unconfirmed)
As per comment #6, closing the issue as wontFix.

Thanks...!!
►

Sign in to add a comment