Hixie brainbuster for what happens with various HTML markup incantations when they are represented through the DOM. Notable for the comment thread. Also the "It's amazing that the pile of shit that is the Web platform survives." comment. So true.

ahh, global scope pollution rears its ugly head in interesting ways.

for document fragments

Trident's Key event flow-chart

Safari sets the nodeName for <groß> to GROSS in the DOM. So document.getElementsByTagName("groß") works but document.getElementsByTagName("GROSS") doesn't. This would seemingly be because Unicode says that the uppercase value for ß is "SS". (Opera 10 uses unicode lowercasing. Firefox 3 does unicode uppercasing, but preserves the eszett.)

"Don't cross the streams"

"phpQuery is a server-side, chainable, CSS3 selector driven Document Object Model (DOM) API based on jQuery JavaScript Library."

"Crowbar is a web scraping environment based on the use of a server-side headless mozilla-based browser. Its purpose is to allow running javascript scrapers against a DOM to automate web sites scraping but avoiding all the syntax normalization issues."

"Timing issues are the source of some of the most devious bugs in JavaScript applications. Problems that never show up during development might surface when the application is used by an end-user on a slow computer or with low bandwidth. Such issues may also be intermittent and difficult to reproduce."

Ahh, my favorite subject... document.write. This is an oldie that I had to reference this evening.

Well I guess this is as good as it gets for a DOM Touch reference

Was this ever fun to find out on my own.

Wow .NET is still this backwards out of the box? I remember now why I was very annoyed with it. I think I even filed a bug report about this with my MSDN account from twenty thousand (ok, 6) years ago.

Draft DOM Core spec work

For cases like document.createElement('<x y z=a x x y u>'); OR document.createElement('<iframe frameborder="0">');

"The interface objects (constructors) and interface prototype objects defined for Beta2 are based on the structure and function of IE's internal object model. Early on, we had to decide if we wanted to implement a "fake" layer for the constructor/prototype objects that looked identical to the W3C model, or to expose what we had, warts and all. While the warts weren't particularly attractive, they do help to bring clarity to the way that the DOM is represented internally and avoid having a whole series of internal mapping bugs between what is actual and what is veneer."

"An HTML DOM parser written in PHP5+ let you manipulate HTML in a very easy way! Require PHP 5+. Supports invalid HTML. Find tags on an HTML page with selectors just like jQuery. Extract contents from HTML in a single line."

It is believed that no known web browsers implement this... <sarcasm>can't imagine why</sarcasm>. This an example of an underspecifed feature - pay attention to the language used as to whether you should rename or replace elements & attributes.

A necessary tool when debugging browser behavior.

"You have an element in the DOM sitting somewhere below the fold (see above the fold), and you’d like to know when it has breached through the bottom threshold of your screen as a user is scrolling down a page."

"Shows the differences between onClick and onChange event between browsers. Use this page in IE as well as any other browser to see the differences."

DOM's Range functions are a smarter way to grab user defined text selections from HTML documents.