|
|
Re: Content-type for XHTML (was: XMLC, setEnableXTHMLCompatibilty): msg#00030java.enhydra.xmlc
On Wednesday 08 October 2003 12:38, Jacob Kjome wrote: > In essence, you are right that Mozilla should be picking up the default > namespace when parsing an XHTML document (with the XML parser) which > provides the XHTML dtd, without requiring it to be specified in the <html> > element. Given this buggy behavior, you should probably provide it anyway > and the overall solution that I documented in my previous email still > stands. Fair enough, but I can also submit a Mozilla bug report... > > > Jake > > > > _______________________________________________ > XMLC mailing list > XMLC@xxxxxxxxxxx > http://www.enhydra.org/mailman/listinfo.cgi/xmlc
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Content-type for XHTML (was: XMLC, setEnableXTHMLCompatibilty), David Corbin |
|---|---|
| Next by Date: | Re: Content-type for XHTML (was: XMLC, setEnableXTHMLCompatibilty), Jacob Kjome |
| Previous by Thread: | Re: Content-type for XHTML (was: XMLC, setEnableXTHMLCompatibilty), Jacob Kjome |
| Next by Thread: | Re: Content-type for XHTML (was: XMLC, setEnableXTHMLCompatibilty), Jacob Kjome |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |