No matter what the root cause here is, I think it would it still make sense to
check for null in getAttribute*() methods in HTMLElement. No matter what DOM
normalization issues continue to exist, this simple change allows normalization
to succeed. The rest of the issues can be addressed as they
Hi Jake,
The code you found in DOMNormalizer is looping over the attributes in the
document not all of the possible attributes in the DTD. If a defaulted
attribute is missing from the DOM then there's probably a bug somewhere
else in the class which wouldn't surprise me. Around this time last y
Based on something Michael Glavassevich said about validating an HTML
document in memory using normalizeDocument() [1] (to get "id"
attributes registered as type "ID", for optimized getElementById()
lookup), I tried an experiment. I parsed an HTML document using the
Xerces DOMParser, providi
