Re: default for using ' in OutputOptions?

V ?, 26. 06. 2003 v 17:45, Jacob Kjome napsal:

> was that XMLC didn't provide a mechanism for all the compatibility issues 
> that might come up.  Now it does.  That doesn't mean quirks to provide 
> compatibility for certain browsers should be on by default.

I agree.

> For instance, 
> the get/setDropHtmlSpanIds() option was forced to "true" in the 
> HTMLFormatter even though it's default in OutputOptions was 
> "false".  Dropping id's on <span> tags is not desired behavior in most 
> cases.  The only reason it was ever done is to get around a bug In IE4.0 
> (which is old news at this point) which only occurred if you were using 
> Keep-alive connections.  Having it as an option available to enable this 
> compatibility quirk is a good thing, but having it on by default just 
> causes confusion and, again, is not the desired behavior in most cases.

This is a very good example for not enabling quirks by default (I myself
run into troubles thanks to these dropped IDs).

> So, you are suggesting that we determine some default behavior that works 
> with the majority of browsers out there and base the defaults quirks on 
> that?

No. I just suggest/ask kindly to provide a very clean documentation for
the projects that include and use XMLC (for example my favourite one -
Enhydra), so that the other application developers in future won't have
to fight the very same problems I faced when I tried to actually *use*
the XHTML in todays browsers.

In other words, I agree with the non-quirks settings so that stock XMLC
produces 100% pure XML, but at the same time I wish the Enhydra worked
out-of-the-box and to generated 100% *compatible* XHTML/HTML (for todays
standard of browsers, i.e. IE 6/Gecko browsers generation).

Here I assume it's possible for Enhydra to modify the OutputOptions
internally since the document.writeDOM() is Enhydra's method, right? So
the guys at Enhydra team need to know what XMLC quirks to enable - and
for this I'd like to see the clear bit of documentation.

Thanks for listening. I haven't done a bit of work on XMLC so my voice
can't be as strong as yours but I think I got a point above.

Petr