Problem:
When I look for the id of an ASP.NET element with some sort of neat DOM querying language I can't find it.

Solution:
Remember ASP.NETer's ASP.NET renames the id from what you named it to something different when it writes the element out to the page. The good news is ASP.NET always names it to the same unique name (something like but not necessarily  ctl00_classname_controlname). Knowing this, you can run your page once and grab the id from the page source. Now use your super cool DOM querying language of choice to find that id by it's new proper ASP.NET name.

Explanation:
Why does ASP.NET do this? The good super geeks at Microsoft know that most of us, not you the reader of course, are not wise enough to give each ASP.NET element a unique name so they won't conflict with each other when ASP.NET is doing all its little magic tricks.

Once again this is a stupid little error that hung me up for more than I'd like to admit. I knew ASP.NET did this I just didn't piece together on why I couldn't find the element by id with my querying language.