I've always appreciated these tools: Expresso and XPath Builder. They make designing regular expressions and XPath selectors almost fun! Did I say fun? I meant less painful. Being able to paste/load text and then interactively play with the search criteria is infinitely better than the code/compile/run/test cycle. It's faster and you get a much better feel for how the expressions work.
So, I decided to make my own interactive tool to test jQuery selectors: jQuery Selector Tester.
Here's a sneak peek:
Note: There are some existing tools you may like better:
My tool is different:
- It is one page. You can save it and run it locally without a Web Server.
- It shows the results as a list of iterated objects instead of highlighted html.
- A cheat sheet is on the same page as the tester which is handy.
I couldn't upload an .htm or .html file to this site so I hosted it on my personal site here: jQuery Selector Tester.
To make the interactive search work, I added a hidden div to the page:
<!--<span class="code-comment">Hidden div holds DOM elements for jQuery to search--></span>
<div id="HiddenDiv" style="display: none">
When ready to search, the searchable html text is copied into the hidden div…this renders the DOM tree in the hidden div:
var Html = $("#TextAreaHTML").val();
When doing a search, I modify the search pattern to look only in the HiddenDiv. To do that, I put a space between the patterns. The space is the Ancestor operator (see the Cheat Sheet):
var SearchString = "#HiddenDiv " + SearchPattern;
var $FoundItems = $(SearchString);
Big Fat Stinking Faux Pas:
I was about to publish this article when I made a big mistake: I tested the tool with Mozilla Firefox. It blew up…it blew up real good. In the past I’ve only had to target IE so this was quite a revelation.
Then jQuery came along and all was good. It was browser independent and freed us from the tedium of worrying about version N of the Acme browser.
I had used outerHTML to display the selected elements. The problem is Mozilla FireFox doesn’t implement outerHTML.
I replaced this:
var OuterHtml = $('<div/>').text(this.outerHTML).html();
var Html = $('<div>').append(this).html();
var OuterHtml = $('<div>').text(Html).html();
Another problem was that Mozilla Firefox doesn’t implement srcElement.
I replaced this:
var Row = e.srcElement.parentNode;
var Row = e.target.parentNode;
Another problem was the indexing. The browsers have different ways of indexing.
I replaced this:
var Cell = Row.childNodes;
var Cell = $(Row).find("TD:nth-child(2)");
var CellText = Cell.text();
So much for the myth of browser independence. Was I overly optimistic and gullible? I don’t think so. And when I get my millions from the deposed Nigerian prince I sent money to, you’ll see that having faith is not futile.
My goal was to have a single standalone file. I tried to keep the features and CSS to a minimum–adding only enough to make it useful and visually pleasing.
When testing, I often thought there was a problem with the jQuery selector. Invariable it was invalid html code. If your results aren't what you expect, don't assume it's the jQuery selector pattern: The html may be invalid.
To help in development and testing, I added a double-click handler to the rows in the Cheat Sheet table. If you double-click a row, the search pattern is put in the search box, a search is performed and the page is scrolled so you can see the results. I left the test html and code in the page.
If you are using a CDN (non-local) version of the jQuery library, the designer in Visual Studio becomes extremely slow. That's why there are two version of the library in the header and one is commented out.
For reference, here is the jQuery documentation on selectors:
Here is a much more comprehensive list of CSS selectors (which jQuery uses):
I hope someone finds this useful.