Chrome Version 45.0.2454.85 m.
All of a sudden one day Inspect Element option in right button context menu greyed out. Ctrl + Shift + I doesn't do anything and F12 doesn't do anything. Cleaned the cache as suggested by one answer here but that didn't help either.
I found out that for strange reasons, either Windows update or Chrome update changed this registry setting.
Software/Policies/Google/Chrome/DeveloperToolsDisabled to 1. Changed it to 0 and restarted the system.
go to your software, then go into policies, google ,chrome ,then you see DeveloperToolsDisabled is at 1, change it to 0. DONE
Related
the system is WIN10, when I open the chrome's developer mode , a little while,there comes out a message ,similarly like this :"we have chinese version" , I want to look for details, but unfortunately I click " Do not show this again".
The position is this picture's red character's position.
this is the picture
So I want to know how to get this message again, and where to setup the reminder?
Thank you so much!
Regards!
Reset Chrome settings to default
On your computer, open Chrome.
At the top right, click More Settings. Advanced. On Chromebook, Linux, and Mac: Click Reset settings Restore settings to their original defaults. Reset settings. On Windows: Click Reset and cleanup Reset settings to their original defaults. Reset settings.
This usually works for me :) let me know how it goes
Not sure what exact message are you referring to, but you can configure much of aspects of developer console via settings (Shift + ? on my computer or clicking on cog icon in top right corner)
There is also Restore defaults and reload button which should get rid of anything you overridden before:
I have recently started to see a frequent error in Chrome Dev Tools when right clicking on an element for the purposes of selecting "Inspect Element" - instead of selecting the element on the "Elements" tab the error "Uncaught Error: Parameter 2 (message) is required." appears in the "Sources" tab for a virtual "extensions:: schemaUtils" script.
The error occurs in the function "validate" as per the screenshot below.
This error seems to occur since installing the "OneTab" extension, and indeed goes away when I disable it. I have reported it to the extension author, so far without response. Unfortunately as work have seen fit to issue me with an underpowered machine, removing OneTab is not an option as memory otherwise runs in extremely short supply.
The issue is easy to replicate, within Stack Overflow itself click on the "StackExchange" icon top left, and then right click on one of the "Your Communities" items. The context menu does not open and the above error appears. This also affects the pop-out menus on the primary product I am working on.
This error only occurs in a single instance of Chrome, which happens to be my primary developer machine, and does not occur on Chrome Canary on the same computer, and with the same extension installed.
Chrome 37.0.2024.2m on a Windows 7 Professional, Service Pack 1, x64 laptop.
Do I have a corrupted copy of Chrome? Can other users replicate this error (with or without the OneTab extension)? Is there anything short of removing the extension permanently that I can do to restore essential "Inspect Element" functionality?
I have already tried resetting Chrome within the settings menu.
The problem you're experiencing is that a breakpoint is triggered for (uncaught) errors.
To stop this from happening, open the Sources tab of the developer tools, and make sure that the circle with the two stripes in it is GREY, not blue. This circle means "Pause on exception" and is the right-most icon in the next picture.
Just stating more clearly : if you are ok with that, just disable the OneTab Chrome extension.
de-activating and re-activating breakpoints in the devtools solved my issue
The breakpoints icon is in Developer Tools, on the Sources tab, the icon left of the pause button.
I also use OneTab, am on OSX 10.10.5, Google Chrome Version 46.0.2490.71 (64-bit) - other extensions I have installed are LastPass, Xdebug helper, JetBrains, Postman, DevTools Theme: Zero Dark Matrix, Google Docs (and similar)
The breakpoints solution was suggested here https://stackoverflow.com/a/25623760/1875965
You started the validation at i + 1, it should be i.
Change:
var message = "Invalid Argument for " + (i + 1) + ".";
Into:
var message = "Invalid Argument for " + (i) + ".";
I have recently started to see a frequent error in Chrome Dev Tools when right clicking on an element for the purposes of selecting "Inspect Element" - instead of selecting the element on the "Elements" tab the error "Uncaught Error: Parameter 2 (message) is required." appears in the "Sources" tab for a virtual "extensions:: schemaUtils" script.
The error occurs in the function "validate" as per the screenshot below.
This error seems to occur since installing the "OneTab" extension, and indeed goes away when I disable it. I have reported it to the extension author, so far without response. Unfortunately as work have seen fit to issue me with an underpowered machine, removing OneTab is not an option as memory otherwise runs in extremely short supply.
The issue is easy to replicate, within Stack Overflow itself click on the "StackExchange" icon top left, and then right click on one of the "Your Communities" items. The context menu does not open and the above error appears. This also affects the pop-out menus on the primary product I am working on.
This error only occurs in a single instance of Chrome, which happens to be my primary developer machine, and does not occur on Chrome Canary on the same computer, and with the same extension installed.
Chrome 37.0.2024.2m on a Windows 7 Professional, Service Pack 1, x64 laptop.
Do I have a corrupted copy of Chrome? Can other users replicate this error (with or without the OneTab extension)? Is there anything short of removing the extension permanently that I can do to restore essential "Inspect Element" functionality?
I have already tried resetting Chrome within the settings menu.
The problem you're experiencing is that a breakpoint is triggered for (uncaught) errors.
To stop this from happening, open the Sources tab of the developer tools, and make sure that the circle with the two stripes in it is GREY, not blue. This circle means "Pause on exception" and is the right-most icon in the next picture.
Just stating more clearly : if you are ok with that, just disable the OneTab Chrome extension.
de-activating and re-activating breakpoints in the devtools solved my issue
The breakpoints icon is in Developer Tools, on the Sources tab, the icon left of the pause button.
I also use OneTab, am on OSX 10.10.5, Google Chrome Version 46.0.2490.71 (64-bit) - other extensions I have installed are LastPass, Xdebug helper, JetBrains, Postman, DevTools Theme: Zero Dark Matrix, Google Docs (and similar)
The breakpoints solution was suggested here https://stackoverflow.com/a/25623760/1875965
You started the validation at i + 1, it should be i.
Change:
var message = "Invalid Argument for " + (i + 1) + ".";
Into:
var message = "Invalid Argument for " + (i) + ".";
Since its inception few years back, Chrome has become a de-facto IDE for web development. I've been using it's Canary(Version 28.0.1464.0) channel for quite a bit and been happy as a clam.
Only issue that keeps bothering me is the lack of ability to have the DevTools console pane, auto scroll to the last message added. I understand that many folks would prefer to have the current behavior. However I was wondering: Does anyone knows how (if even possible with the current release) to flip the switch and have the console auto-scroll?
Thanks.
Clearing the console and scrolling the bar down to the bottom didn't work for me.
The problem was that I had zoomed out DevTools.
Solution:
Focus the DevTools, e.g. by clicking on the console's > prompt
Hit Ctrl-0 (zero) on Windows, or Cmd-0 (zero) on OS X, to restore the default font-size
Hopefully then auto-scroll to bottom will start working again!
Thanks to this guy for pointing it out:
http://code.google.com/p/chromium/issues/detail?id=161646#c5
One Reason why it's happening:
Logging of HTML elements into the console makes the console view lose the last console message.
How to solve it:
Instead of doing something like this:
console.log("Some logging message:", html_element)
try this (wrapped the messages with brackets)
console.log(["Some logging message:", html_element])
It drove me crazy too and I found the solution here:
Google Chrome follow developer console logging
With the console open, drag the scroll bar down to the bottom of the
window and release it. It should tail the output for you.
It does not matter if you have the console docked or not.
Working for me on a osx 10.8.5 and chrome 31
In Chrome version 29.0.1547.76 m, it auto-scrolls when you undock the console. It stops auto-scrolling if you click on the console, then you'll have to clear the console before auto-scroll will be ready to start again.
The "Undock into separate window." button is the bottom-left most button of the console.
For me I've noticed that the autoscroll stopped when the console showed a warning so I've filtered out the warnings and all is good:
For me the only solution that worked was:
click F1 (settings)
At the bottom restore defaults and reload.
None of the above worked.
I found this solution in Chrome 49+
Go Dev-tools/ Settings /
"Console tab"
x Preserve log upon navigation.
Done!
How to remove all breakpoints in one step in Google Chrome? Using version 11.
[update]
There is now a feature request for this.
[update]
The feature request is closed (Dec 2011)!
This is now possible in Sources tab of Chrome Developer Tools.
Please see screen grab below and right click within the "Breakpoints" section of the left window.
Since recently (Chrome 18), you can right-click any breakpoint in the Breakpoints pane and voila! The "Remove All JavaScript Breakpoints" popup menu item!
Chrome Devtools crashed everytime I tried to access the Sources panel because of a breakpoint on a minified Javascript file.
To remove all breakpoints without access to the interface, you can do the following:
Open inspector-on-inspector : undock first inspector and hit ctrl+shift+i to open the second
On the inspector-on-inspector console, execute the following:
window.localStorage.breakpoints = [];
Close the inspectors and reload the page. Now the breakpoints are gone.
Under Sources, you can click button marked with red on picture below or use shortcut Ctrl + F8 just like tool tip is showing (activate / deactivate breakpoints). A little bit lower under 'Breakpoints' you will see all your breakpoints. If you choose to disable all, they will be grayed out.
solution here.
To purge all breakpoints open inspector on inspector (undock first
inspector and hit ctrl-shift-I to open the second) and run
"WebInspector.settings.domBreakpoints.set([])" in second inspector's
console.
new Tabs; Ctrl+Shift+J to Console; Access URL
Open the Chrome task manager and end the tab page.
Ctrl+Shift+J to Application -> Service Workers (Offiline) -> Refresh
to Sources Cancel Breakpoint
Success
Another option is to de-activate all break points using:
Ctrl + F8
In my case Uninstall and new installation of Chrome was without any success.
Also window.localStorage.clear() did not help.
My "last chance solution" is to remove entire directory where Chrome is storing its data.
First turn off your Chrome.
Then look at this path "c:\Users\ {your_user} \AppData\Local\Google\Chrome\User Data\Default\Local Storage\". Here try to delete all what is in this directory.
You can also clear all inspector settings and reload the inspector. It helped me with fantom breakpoint I could not remove in any other way. Open inspector and go to Preferences -> Sync -> Restore defaults and reload (at the bottom).
Step 1: Go to Developer tools and expand Breakpoint section
Step 2: Right click on expanded area of breakpint and there will be many options lik