> But unlike Tidy, a browser does not need to correct the DOM, since a > decoration applies to how fonts are rendered it can produce the right > rendering while producing an OpenXML-equivalent DOM in memory. > Once scripting shows up, things get rough again, though.
I have an open question on a related issue. Browsers handle forms that overlap subtrees. If you submit the form, the right parameters go out. With a DOM and the current spec for HTML, how do you do that? I haven't studied XHTML in depth, but I imagine the enforced XML rules would invalidate many forms in current web pages. I think there may be cases where certain layouts (without using CSS-P) require incorrectly placed FORM tags or _extreme_ ingenuity on the part of the page designer. Are there any (standardized) mechanisms for dealing with this? (Basically, I bring this up since I bet Apache's Java HTML engine could easily be the default for Java coding in a year or two, and being able to deal with some of these issues could be important.) - Tom
