Better, Stronger, Safer jQuerify Bookmarklet. A long time ago I built myself a little bookmarklet to load jQuery on pages that don't already have it. The idea was to allow me to play around with any page on the web, using jQuery in the Firebug (and now Safari or IE8) console. I blogged about it, got lots of great feedback, and then blogged about an improved version. Now that a lot more great feedback has come through the comments of the updated bookmarklet post, I've decided to update it one more time.
The Bookmarklet Update: May 7, 2012 Apparently, Safari 5.1 is stricter than other browsers in its enforcement of URL encoding for bookmarklets. To use the bookmarklet, drag the following link to your bookmark/favorites list: Then, when you're on a page in which you want to play around with jQuery in the console, just click the bookmarklet. Problems with the Other One A Few Improvements in This One To handle the problems, I'm having the script do a few things differently: Update. Download details: Internet Explorer Developer Toolbar.
FireQuery is a Firebug extension for jQuery development. 10 Reasons Why You Should Be Using Firebug - Nettuts. Firebug is one of the most popular tools used by web developers. In this article, we'll take a closer look at ten of its most attractive features. 1. Console The first thing you're going to notice when opening Firebug (either from the status bar or using the ctrl+F12 key combination) will be the Console panel. After a quick look, one might think that it is an alternate version of the Error Console (Ctrl+Shift+J). Logging of errors, warnings and noticesability to run Javascript code But Firebug extends the Firefox functionality, so it can do much more, such as: logging errors for Javascript, CSS, XML, XMLHttpRequest (AJAX) and Chrome (Firefox internals)run Javascript code upon the current webpageadditional Javascript object is put at disposal (console) Let's look over some examples built upon the console object.
This will generate the following result. This button is equivalent to the "Inspect Element" in a webpage context menu. 4. The same as HTML->DOM. 6. Performance Testing Three step. 7.