Trying to view my test localStorage, I see nothing in the Storage section under Applications in the Developer Tools.
However, using the console, I can access it, meaning its clearly there.
Am I missing something or does this seem to be a bug I couldn't find anything about?
I am using Chromium Version 57.0.2978.0 (64-bit)
Its a known Bug (#701413)
They fixed it in version 59.0.3069.0 (#718482)
I can see the localStorage of different domains like FB, but not from the current domain. When starting up developer tools it appears, but disappears after a reload.
I have been encountering the same issue. Not a great solution, but if one closes the developer tools and reopens the developer tools, one will find the domain showing again under Local Storage with all the local storage name value pairs. At least I found a nice shortcut to open and close the developer tools researching this issue. cmd + option + i for mac. I hope this helps my fellow coders. Chrome Version 57.0.2987.133 (64-bit) MacOS.
Workaround: re-open the Dev Tool, that is press F12 twice. Tested on Ubuntu Chrome 58.
I have encountered the same issue on my MAC. Open settings in dev tools and restore to the default view.
Related
Now that Firebug has been subsumed into Firefox, how can I configure the browser to bring Javascript errors to my attention without having the console open all the time, as Firebug used to do by showing an error count on its toolbar icon?
The Firefox DevTools provide a so-called "Developer Toolbar" aka GCLI (openable via Firefox menu > Developer > Developer Toolbar or Shift + F2), which displays the number of errors on the page (besides providing many useful commands):
Update:
The DevTools team obviously plans to remove the Developer Toolbar, because of low usage and because it's unmaintained and for most of it's features are available somewhere else.
There is no replacement yet for the error count, though, but a comment on the related bug report indicates that it will be added back.
Another options is to use Chrome extension JavaScript Errors Notifier.
To install it in Firefox, you'll first have to install another extension Chrome Store Foxified, which enables you to install any Chrome extension from Chrome Web Store to Firefox. You can follow the instructions of Chrome Store Foxified to install the extensions you like. (Note that not all Chrome extensions will work in Firefox.)
If you want to install the Chrome extension permanently, you'll have to sign up with Mozilla to get the extension signed.
If the JavaScript Errors Notifier extension is successfully installed in Firefox, you'll see an icon appearing at the right end of the address bar.
And when there's any JavaScript error in the page, the icon will turn red. To see the details of the errors, you can click on the icon. And the extension have quite some options to tune the errors that you want to get alerted.
Google Chrome v48.0.2564.116 (64-bit) for Mac OS seems to retain all console commands indefinitely. None of the following have any affect:
clear()
console.clear()
Command-K
turning off "preserve log" and "show all messages"
Clear browsing data, from the beginning of time, all options check marked - removing all cookies
quitting and restarting or shutting down and rebooting.
Any combo of the above.
Unable to locate a chrome_debug.log file anywhere on the system (i.e. logging is not check marked).
Trashing Google Chrome and the associated library files then re-installing got rid of the console history, but the new version nonetheless holds all console subsequent console entries indefinitely.
Any insights? Any idea where this information gets stored?
If you are using windows 10. Just Simply go the console and right click then click on clear console
Thanks to Karmiphuc and the following link:
How to remove all recent console command
which mostly answers the question.
It's slightly understated there that, on Mac OS at least, you have to call the developer tools twice consecutively.
So 1st pull up a browser window, and do Command-Shift-I (Mac shortcut).
Then, making sure the Developer Tools window is undocked, do a second Command-Shift-I which pulls up yet another Developer Tools window.
Now look under Local Storage > chrome-devtools://devtools > consoleHistory.
I used to be able to debug javascript from webstorm with no problem at all.
Thanks to the jetbrains chrome extension, it simply opened a new tab in chrome and launched my site in there with no problem whatsoever.
But recently I had to reboot my computer (with a beloved windows update) and now this is not working anymore.
When I start the debugging from webstorm chromes opens a new tab and I see the following in the address bar and then nothing...
data:text/html;base64,PCFET0NUWVBFIGh0bWw+PHRpdGxlPkxvYWRpbmcgaHR0cDovL3ZtLnNob3RndW4ubG9jYWwvPC90aXRsZT4=
My site is not opened and the page remains blank in chrome.
Most probably this is a result of Chrome update: some Chrome API changes introduced in v.37 break js debugger. WEB-12418 is fixed in WebStorm 9 EAP
Does anyone know how to get access to the network traffic (requests and responses) caused by a document in a browser window from a xpi Firefox extension, programmatically?
I'd like to use the information you'll see on 'Network' tabs in current browser developer tools (like Firebug or Chrome Dev Tools). Basically, I want to build a Firefox extension that tracks some special web-bugs and do some more analysis on this data.
I've checked the API documentation of the Firefox Addon SDK but I couldn't find the information I was looking for.
Can anyone tell me how this can be accomplished using the Firefox Addon SDK?
Thanks for any hints.
I'm trying to use Firebug to debug a JavaScript file in an extension I've added to Fx 4.
Can anyone tell me how to do it? I can only see website scripts.
Use Chromebug it's firebug for extension development, witch will give you the full ability to inspect debug firefox it self and all firefox extension as if it's a webpage :)
1- install the latest version from here: http://getfirebug.com/releases/chromebug/
2- Winkey+R to open run then type firefox.exe -chromebug this will run firefox with chromebug
3- for more information visit http://getfirebug.com/wiki/index.php/Chromebug
Please see MDN - Building An Extension - Debugging Extensions, which shows what tools Firefox provides you with to natively debug extension, also take a look at Dive Into Greasemonkey - Debugging User Scripts (PDF, p.13) which is aimed more specifically at your request.
Other than that, see How to debug a Greasemonkey script with the Firebug extension?
On Firefox 19 or later, it's possible to use the built-in JS debugger on the browser itself. Go to about:config and set the following two prefs:
devtools.chrome.enabled: true
devtools.debugger.remote-enabled: true
After you restart the browser, you can access the Browser Debugger through Tools > Web Developer > Browser Toolbox.
(note that you must accept the incoming connection)
See more at: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_JavaScript#JavaScript_Debugger
In the bottom right hand corner there should be a little Firebug icon. Single or double click to open then you see some tabs at the top. Click the "Console" tab for real time debugging, or the "SCript" tab to view the scripts that have been loaded. Note, you can also load CSS and HTML through Firebug, use the "Viewer" icon to view HTML code on the page in real time.