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.
Related
I'm sorry this question might not be completely on topic, but i couldn't find answers googling it.
I'm creating an google app script (with clasp).
When i run the script i get the following popup as usual:
I'm supposed to click on advance and go anways.
But the advanced button no longer works! it doesn't show me the followup button to continue anymore!
Does anyone have the same issue and was able to fix it? It seems to have originated after the chrome update (with rounded ui).
I tried deleting the original grant (i added a feature that needed bigger scope), but even that didn't work.
It might be one of my chrome extensions.
Doing the same thing in incognito mode, worked!
I'm not able to see the errors during the debug of my app on chrome please help with settings.
Even after checking the 'Errors' under 'Default', I was not able to see the errors in the console.
I then navigated to settings (or press F1) and on the bottom of the page, you will see 'Restore defaults and reload' option.
After restoring to defaults, I am able to see the console errors.
I hope this helps someone. In my case, none of the above solutions helped. The culprit was the filter text field shown in the below image.
Clear the text field and the errors will be shown again.
Solution :-
See The Right Side Of Image
Explanation :-
You Will See A Default Levels Drop down List
Check The List Items According To Your Needs
If none of these solutions work for you, remove the text in the "filter" box.
Select the Verbose option in the Default levels dropdown menu.
I had "18 hidden" in Chrome, but could not inspect what I at the time thought was errors. Turns out I simply had not checked all logging levels. You will of course get more hidden log-messages the fewer logging levels you have checked.
Make sure 'Selected context only' option is deselected.
Chrome creates context not only for current page, but also for embedded iframes and browser extensions. This could narrow visibility of logs. This was the case for me.
devtools screenshot
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!
So i've been banging my head against the wall trying to figure this out, and it's about time I ask for help. I have a flash audio recorder that is displaying a popup to the user asking them to allow microphone access using:
AS3 --
Security.showSettings(SecurityPanel.PRIVACY);
Now, on chrome it works perfect! Everything shows up correctly and looks like this:
http://postimage.org/image/6e6ldfmpj/
Great. Now the issue is, on Firefox (and I believe IE9) it looks like:
http://postimage.org/image/mqp1kmcjj/
Notice how there are only 3 tabs in the second one (Firefox). Well, the second tab over is Privacy and allows you to "allow" or "deny" our website from accessing your mic. So it's a bit of an issue that that tab is not even visible... Any thoughts on that? I can't seem to find anywhere where anyone has had that same flash dialog box pop up with only 3 tabs.
Thanks in advance!
You can use [Allow][Deny] dialog:
It appears whenever you access microphone/camera by attaching them to NetStream.
Related question on stackoverflow:
allow deny remember flash security panel
As Sunil D. mentioned above, Firefox will not show some tabs in private/incognito mode. The problem is user can turn it on not only by opening new private window, but also by changing some regular Firefox preferences. Go to Firefox options, select "Privacy" tab and search for "History" group. There you will see a dropdown with "Firefox will:" label. There you can select "Never remember history" item and browser will show you a small tip:
Firefox will use the same settings as private browsing, and will not remember any history as you browse the Web.
Then your browser will be restarted. Further research revealed that Firefox really turns private mode on after such manipulations. Sunil D. and Jordan Reiter were both right - the problem can happen with users in private mode and problem can be solved by reinstalling Firefox with all it's configurations (including that history setting). Of course, it's much easier to ask users to change that setting. Also private mode detection with JavaScript can help to inform user about this expected problem.