How could I get Chrome Extensions off when I inspect web elements? - debugging

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.

Related

Scraping an Angular website with selenium and C# returns the angular script, not the rendered web page

This seems to be by design as far as I can tell. Selenium can see the initially loaded HTML, but not the HTML after it's been massaged. I've tried IE, Chrome and PhantomJS and they all show the same behavior. So does the built-in Chrome debugger, until you inspect an element on the page, you can't query any of the rendered HTML.
I'm looking for any suggestions about how to scrape the web page. The only option I see right now is finding the chrome process, triggering the inspector, clicking inside, then running the Javascript. Needless to say, this sounds fragile.
I also haven't been able to find anything on capturing the Ajax calls from selenium so I can make them and capture the JSON. When tried copy / paste from the chrome network tab into selenium I got a missing application block message.
Does anyone have any other advice?
Since I can replicate the issue in the chrome debugger, I don't see posting code as useful. It looks like a design decision.
Ralph
Sadly, I wasn't able to do things in a straightforward way. Instead, I used Selenium to do the login and navigate to the page, then use windows API calls to click inside the window send ^a^c to copy the data and an absolute location to click on the button to go to the next page.
The site is set up so that ^a^c copies the raw data for this site. I don't know if that's standard for Angular or not.
Fragile, but it works.

Is there a DOM Inspector like Chromes for Firefox?

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

Inspecting firefox with firebug

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)

Missing icons in Glimpse

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.

View chrome source in Firefox

It would be extremely helpful for developing Firefox extensions if I could see the source of, e.g., chrome://browser/content/browser.xul with overlays applied. Is there a way to do this? Chrome List and "View Source" show only the base structure, ChromeBug requires restarting the browser and isn't too easy to get working.
All you need is DOM Inspector, and I highly recommend pairing that with Inspect Context which adds an "Inspect" option to the right-click menu of almost everything, much like the "Inspect Element" option of Firebug.

Resources