My stack trace is big enough that even fullscreen for the Console doesn't get me to the initial lines.
Is there a way I can scroll up the console lines to be able to see the initial lines?
Many thanks!
If Ctrl + Up/Down doesn't work for you, you can also use Shift + PageUp/PageDown. I think the Ctrl + Up/Down option only works on Macs but I'm not 100% sure.
I came across the same problem with scrolling in their console, and what worked for me most of the time (depending on what command was issued) was outputting the results to a log file.
For example: rails s > rails.log
Then I just open the log file and scroll through it. Hope this helps you!
Related
Since yesterday I have following problem: The variables in session storage are not visible anymore in chrome/devtools under session storage. In the console, I can call the variables, so they're here, but not visible.
So far the only way I could solve this problem is by changing my chrome profile to "gast". Then I can see the variable back. But I don't know which settings should I do to make it work under my regular profile.
Anyone a clue?
I had the same problem and I just solved and it was very simple.
1 - Open devTools and go to Settings
2 - In Preferences roll to the bottom of the page and select the "Restore defaults and reload" option.
I'm seeing the same thing, the localStorage preview sometimes gets stuck and is not updating. Reload or reset of preferences is not helping.
Reported it here: https://bugs.chromium.org/p/chromium/issues/detail?id=1414104
Had the same issue.
My teammates could see data in the application tab, but I could not.
What solved the problem was running:
chrome://restart
in the address bar.
Hope this helps.
I searched around but no answer -->
There is any way to enable tab for indention in chrome devtools console when i'm writing ? for example writing a function,
I need to manually add spaces every time .
I searched in settings but nothing (chrome 50 version)
Tried tab,ctrl-tab,alt-tab.. and so
thanks
I'm pretty sure you found out how to do this by now but if not it's shift + enter. I just played around with it recently and it ended up working for me.
Take care!
I have wasted nearly 4 hours in fixing this.
After Babylon this time it is delta-search which makes my chrome sucks on every new tab. chrome://newtab loads: http://www2.delta-search.com/?babsrc=NT_ss_SU&mntrId=786E00E04C01EE9A&affID=121564&tsp=4987
I am not able to fix this. I have already fixed homepage, search setting and other browsers. Please help me to fix this new tab issue. I want "Most visited tab" to be there when I press new tab button.
A real solution is to reset some fields in "chrome://flags". This was the way I did last time in AVG or Babylon. I have solved my problem but I wish if someone could really give exact steps so that next time if a user gets stuck he can find it here.
:p
open google chrome, type chrome://flags/ on address bar and go to hidden configuration setting.
change following part of configuration file to disable by cliking on enable..
Enable Tab Browser Dragging Windows
Enable creating a browser window when dragging tabs. #enable-tab-browser-dragging
Disable
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!
Im using console.log lots in my javascript for debugging mouse move events. The problem im having is that when in the chrome console the new entries aren't followed.
Its best illustrated in these screenshots:
First lot of logs is fine because its big enough to see all of it on the screen:
A few seconds later:
The log has gone past the size of the window requiring me to scroll.
This makes it incredibly difficult to debug mouse move events because I have to move over to the console and scroll down, thus adding more entries to the log.
So my question is: How can I get chrome to essentially tail the log instead of stopping and require me to scroll.
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 took me quite a few tries to get it to work in Version 27.0.1438.7 dev-m. But in Version 27.0.1440.0 canary, not only did it happen automatically, I could reattach the auto-scroll each time I tried.
You can download Canary from here.
The default behavior is for Console to follow (tail) logs as they head in there.
However, we had a bug in the DevTools where if you changed the zoom factor (cmd++) it didn't work always.
We just fixed that: https://codereview.chromium.org/180733003/ You'll need canary for a little while (from the date of this post) but it'll work its way down to Stable in about 10 weeks.
There's a rather pernicious bug here (present in Chrome for as long as I remember), where if you log any sort of expando-item like a DOM element or some such thing, it messes with the display of the log, and causes the scroll to stop following.
I solved this by applying a little bit of ingenuity, and finding the offending log, and you don't even need to delete the log statement, you just have to make it "friendlier". What works very often is I take any such log statement such as
console.log((mouse ? "mouse" : "touch") + " start on", jqtarg[0]);
and wrap it in an array:
console.log([(mouse_not_touch ? "mouse" : "touch") + " start on", jqtarg[0]]);
You may try do other things as well, in an attempt to make the log more readable, such as an object (haven't tested any of this rigorously, it may still cause the annoying failure-of-scroll-follow):
console.log({"mouse/touch start on": jqtarg[0]});
Based on a very small amount of testing, it would appear that if a log appears in the log buffer as an item that can be directly hovered (as opposed to requiring you to manually expand it first) to cause the inspector to highlight the item in the DOM for you, then it may trigger "scroll lock syndrome".
BTW, a helpful thing to be aware of is that if you log the exact same stuff repeatedly, Chrome helpfully "stacks" them like so: (See? I fixed the autoscroll by shoving my log in an object! yay!)
If you don't really need to see values based on precise coordinates, printing coarser values more ... coarsely will lead to a more compact log (which will still give you sensible feedback with counts).
Update: Sometimes none of this works. Sometimes you're just out of luck with this and you just have to clean up all the logs that you don't need and log the minimal amount of information to prevent overloading it and causing it to fail to scroll down.