nisheeth%netscape.com bfc73dae1e 1) Fixed a mistaken assumption made by the XML error handling code in nsExpatTokenizer. It no longer treats the error location returned by expat as being relative to the current XML chunk being parsed. Instead, the error location is considered to be relative to the start of the XML file. The lengths of incoming XML chunks are added to a new member variable, mBytesParsed. When an error occurs, we subtract mBytesParsed from the error location returned by expat to give us the offset of the error in the XML chunk. ... 2) When nsWellFormedDTD sees an error token, it dumps the error to cerr and notifies the content sink about it. This is a temporary solution. The right behavior is for the browser to show the error in the content window which, currently, happens only for .XML documents. XUL and RDF files use their own content sinks which do not implement error handling. This needs to change so that code is shared among the XML, RDF, and XUL content sinks. I do not want to fix error handling by just cutting and pasting the error handling code from the XML content sink into the RDF and XUL content sinks.		1999-04-06 08:17:03 +00:00
..
expat	Replaced the C++ comments with C comments.	1999-04-05 09:11:11 +00:00
htmlparser	1) Fixed a mistaken assumption made by the XML error handling code in nsExpatTokenizer. It no longer treats the error location returned by expat as being relative to the current XML chunk being parsed. Instead, the error location is considered to be relative to the start of the XML file. The lengths of incoming XML chunks are added to a new member variable, mBytesParsed. When an error occurs, we subtract mBytesParsed from the error location returned by expat to give us the offset of the error in the XML chunk.	1999-04-06 08:17:03 +00:00