I am fairly new to writing code, but I played around with some chrome apps which use WebSQL for DB. I decided to learn IndexedDB, but needed something more visual, to help me out. WebSQL database entries can be easily seen in in resources tab in "debugger", but indexedDB database is not shown there.
Chrome is v17, OS Ubuntu 11.10
Is there a workaround for this( plugin or anything else) ?
If you use Chromium or the dev channel of Chrome you can enable an experimental Dev Tools feature to surface IndexedDB in the Resources panel.
https://plus.google.com/u/0/100132233764003563318/posts/7pbJUZCGk8U
In chrome, click on developer tools or use ctr+shift+I
Click on the application menu
Right click on IndexDB
Click Refresh IndexDB
Then you will see your database content.
The accepted answer is 10 years old, mentioning experimental DevTools. So, I decided to rewrite answer.
In Chrome, press F12 or click application menu > More Tools > Developer Tools to open Chrome Developer tools.
Go to Application tab.
On the menu left, expand IndexedDb under Storage section and you will see your IndexedDb content.
Related
I was recently using the dev tools in Firefox and noticed you could turn on and off certain menus (styles, network, storage, etc.) . When back in the Chrome dev tools, I looked for the same check-boxes / functionality to no avail.
A bit of googling got me no where, nor any answers here. I've read that I could go and manually alter the dev tools in Chrome / make plugins / etc, but was wondering if I just overlooked this feature or if someone has already made this wheel?
Thanks.
Edit: pictures
highlighted firefox dev tool settings
firefox dev tools with added toolbar
I'm the Chrome DevTools technical writer. This feature doesn't exist. I created a feature request here: https://crbug.com/888667
If you want this feature, star the request. The more stars a request gets, the more likely it is that the team will implement the feature.
Is it possible to enable autosave on snippets in chrome dev tools?
It is infuriating when i accidentaly close a tab that dev tools was attached to where i had my snippets open and when i open dev tools again i've lost alot of work!
Are there any flags i can set to enable autosave or somehow get it to save when i run the snippet?
Just to be clear i am talking about the snippets under Sources/Snippets.
I know i can "just" use the shortcut ctrl-s to save however that is simply not good enough, i would atleast expect a recovery like all modern editors deliver.
Incase this cannot be achieved please point me the in direction where i can submit a feature request to the Chrome Dev Team
Select Tools > Developer Tools. The Developer Tools window opens as a docked panel at the side or bottom of Google Chrome. Click the Network tab. Select Preserve log.
Also, go to Settings in devtools, which is a little screw on the top-right corner, find the Console section under Preferences, and click on Preserve log upon navigation.
This has worked for me.
So in the Chrome version of Firebug, it's lying on top of the window, thus, if the whole window has text, you will have stuff hidden behind the firebug. Is it possible to get it to be like Firefox's version, where it is part of the window screen like the developer console? The options don't seem to point to anything that indicates this option.
The Chrome extension of Firebug is based on Firebug Lite, which is a JavaScript that is injected into the website. So, there is unfortunately no way to integrate it into Chrome's UI.
Furthermore, Firebug Lite (and with that the Chrome extension) is unmaintained for several years now, so it doesn't provide the features integrated developer tools have.
Alternatives are:
Chrome DevTools
Chrome has integrated developer tools, which provide a huge amount of features for web developers.
Firefox DevTools
The Firefox developer tools allow to debug Chrome (and other browsers) remotely. This doesn't work as good as the integrated tools and provides less features, but allows you to use the same tools to debug in different browsers.
debugger.html
The debugger.html project (developed by the Firefox DevTools team) picks up the idea of Firebug Lite by providing a browser independent UI. It's based on a local web server serving a website, which allows you to debug JavaScript code in different browsers by connecting to them remotely. Unfortunately, it currently only provides a JavaScript debugger and it's unclear whether it will be extended to cover other features like an HTML inspector panel, a network panel, etc. later.
On my school chromebook developer tools just got disabled or something.
When i right click to inspect an element, the "inspect" button is grayed out and if i click the options button in the top right, go down to more tools the developer tools button is grayed out there too.
Does anyone have any idea what is happening and why it is happening?
(Developer mode is enabled on my chromebook)
On a Chromebook, Chrome Developer Tools is enabled/disabled through Chrome Policies, which is maintained by the Chrome Management Console as part of a Google Work account. In this case, the policy is DeveloperToolsDisabled.
In Windows, it is possible to enable/disable it in the registry, and there is possibly a Preferences file in OSX.
I'm afraid you would need to speak to your school's IT department about this, as they are the only ones with access to these policies.
For the last few years I have been using Firefox, Firebug, and the Web Devevloper Firefox toolbar for all my web dev needs, quite happily. I am, however, very interested in experimenting with moving my web dev support over to Chrome, but I have no idea where or how to start. How much functionality is build into Chrome and how do I access it? What add-ins do I need and where do I learn about using them?
These are two of many questions I think face most web devs moving into a much less familiar environment. I'm trying to ask a broader question here, along the lines of, what do I need to use and know for effective web deb and JavaScript debugging in Chrome and where is best to learn what I need to?
Google Chrome (as well as Safari) has really underestimated Developer Tools feature. Lots of developers are indifferent to it and use Firebug through habit. (to no purpose!)
But for me it is the main debug tool: it looks more pleasant than the latter and includes a way cooler features. (e.g. Timeline — separate time intervals for Loading, Scripting and Rendering).
Developer Tools Tutorial.
Can't give up with Firebug? Have a look — Firebug Lite.
More tools.
→ Webmaster tools;
→ Speedtracer;
→ Page Speed.
→ From google webmasters-faq:
There are several tools to help you test your website in Google Chrome:
Web Inspector
Right-click on any component on a web page to launch the web inspector. You'll be able to see the elements and resources associated with the component on which you clicked, including a hierarchy view of the DOM and a JavaScript console.
Task Manager
Select the Page menu icon, then Developer > Task Manager (or press Shift+Esc). The task manager shows all running Google Chrome processes, and the resources that they're using (memory, CPU, and network).
JavaScript Debugger
Select the Page menu icon, then Developer > Debug JavaScript. This launches a JavaScript debugger that can be used to attach to existing processes.
in chrome: right click and "Inspect Element"
the Light Version of Firebug is available too.
While in Chrome, press Ctrl+Shift+I and start experimenting. It's all you'll need.
The Web Developer port from Firefox is very handy.