I really dislike Firefox DOM Inspector. Is there one that docks to the page so I don't have two separate windows and also highlights the box/margins/padding like Chrome/Safari does? I can't find one.
Firebug is the best tool for web development missions:
http://getfirebug.com/
Once you get used to it, there is also a (Lite) version for Chrome:
http://getfirebug.com/releases/lite/chrome/
Recent versions of Firefox have it built in. Here is how to open it:
Ctrl+Shift+i (Windows)
Command+Shift+i (OSX)
References
Firefox Tool Shortcuts
Related
Note: This is the EXACT same question as this, but for FireFox.
Is there a way to "force" the tab to think that it is in or out of focus, like toggle pseudo classes in Developer Tools, but for the entire tab.
I am running FireFox on Windows 10. I could not find a way to do this using Developer Tools, and do not want to setup a whole testing framework just for such a simple thing.
Thank you for your time.
In the Firefox DevTools this is not possible (as of Firefox 67), so I've created an enhancement request to add this feature.
I am quite sure that with the good old Firebug, it was shown in the Layout tab, together with the box-sizing property.
Is it possible to tell in the Web Developer too? There is a Box Model tab which is quite similar to the Layout tab of Firebug, but it does not show this information.
Btw: I thought the built-in Web Developer was built on Firebug, but when reading about it it actually seems that they are two quite separate things.
That feature is currently only available in Firefox Nightly.
I had installed dozen of Chrome Extensions.
But when I "right click" > "inspect element" in Chrome to check my html structure,
I don't want to see anything from Extensions.
here is a simple page debugger view in Firefox & in Chrome.
clear and pretty in Firebug:
chaos in Chrome:
I just need a clear view in Chrome debugger :-(
Till date there is no way to isolate DOM view from Chrome Developer Tools barring Chrome Extensions.
Work Around #1:
I suggest you to Open page in Incognito Mode, where your extensions are (Most probably) inactive this eliminates extension code being visible in DOM.
Work Around #2:
Create another profile for Chrome Browser, where you can find pure DOM View.
Using ColorZilla I found an interesting feature. If I pick a color from firefox (bars,tabs or anything else of the browser) and then go to:
ColorZilla > Inspect Last Element > In
Firebug
Then I can see the markup,css,js that firefox uses in the firebug panel just like a website.
Is there any solution to view this code without use Colorzilla?
As mentioned in the comments, Chromebug is no longer working with current Firefox versions. Instead of opening the limited chrome://browser/content/browser.xul page, you can make the browser chrome accessible to the scratchpad. Open the about:config page and set devtools.chrome.enabled to true, as described in the extension development environment setup guide on MDN.
Open the JavaScript scratchpad (Shift+F4) and select the browser context environment. Now you can type in something like window or document.getElementById('urlbar') and click the inspect button or hit Ctrl+i. This will evaluate the expression and open the element inspector, which shows all properties of the element.
It sounds like you're after Chromebug.
Chromebug is the Firebug code adapted
for XUL applications. It is the
debugger that Firebug developers use
to develop Firebug.
So you can debug your debugger, you know?
Instructions: http://getfirebug.com/wiki/index.php/Chromebug
There is actually a dedicated version of Firebug for that called Chromebug (Named after the chrome of Firefox, not Google's chrome)
I have just installed Glimpse, and in Google Chrome I am missing a lot of the UI icons (eg, the '+' signs to expand the blocks of details).
Any known fixes? I use Chrome for development as I find it runs faster than FireFox and IE, so it is a bore to guess where the icons are.
Also, no close button for the debugger, and the eye doesn't show when 'minimized'.
#awrigley What version of chrome are you using (currently we have been testing against Chrome 11, Firefox 4 and IE9)?
Also can you navigate to www.yoursite.com/Glimpse/glimpseSprite.png? If you can get to that endpoint can you "Inspect Element" on where you expect the buttons to be and check what chrome thinks the image URL(...) in the style is set to.