Comments: XML Support

Is the XML support supposed to support UTF-16? Or only UTF-8? I've filed a bug via the bug button, but for what it's worth I get an XML Parsing Error when I drop a UTF-16 (with and without BOM) XML file on Safari. With UTF-8 it always works, BOM or not.

Posted by bryan pietrzak at February 13, 2003 7:52 PM

Dave, trust that I'm not seeking to join the ranks of bug commenters. But I started getting an XML Parsing Error only after the 10.2.4 upgrade. A page that loaded stopped loading with the latest Safari beta, only after the upgrade. Isn't that weird?

Posted by Lex at February 13, 2003 7:57 PM

I like how Mozilla handles it. The whole automatic selection thing sounds nice.

Posted by Owen at February 13, 2003 9:04 PM

My Safari hangs on the new "advanced CSS and XML" http://devedge.netscape.com

Anyone able to access DevEdge OK?

Posted by pb at February 13, 2003 10:26 PM

Lex,

It doesn't sound weird at all. Before 60 Safari would load an xhtml page as Tag Soup: now it must be properly conformant (I asume, won't get a chance to try it out until tomorrow).

Try running the page through validator.w3.org.

... of course I could still be misunderstanding you and misdiagnosing the problem.

Posted by nnooiissee at February 13, 2003 10:27 PM

That you are nnooiissee. He means he had v60 and it was doing one thing, then he upgraded to 10.2.4 and it changed *Safari's* behavior.

On the Macintoshian Achaia (Ars Technica) OpenTopic forum, a similar thing happened, only now it refreshes properly after posting. Very odd that an OS point release is changing the behavior of Safari (especially when it apparently didn't touch webcore, etc)

Posted by Rura at February 13, 2003 10:44 PM

Dave, thx for the updates. Here is an interesting article about how Mozilla 1.3 for OS X beta measures against Safari v60 beta.

http://www.applelinks.com/articles/2003/02/20030213131311.shtml

Posted by Jack at February 13, 2003 11:21 PM

Okay, so this really means that you can apply CSS to XML and have it work--presumably arbitrary XML, not just XHTML. I'd assumed it was something closer to Mozilla's, which supports XSLT for styling XML documents--but having tested an XML version of my resume, Safari clearly doesn't do that.

I've never tried styling arbitrary XML with CSS, with any browser. If that's what WebCore actually does, that could be very cool for an as-yet-mythical project I'm contemplating.

Posted by Watts Martin at February 14, 2003 12:18 AM

For the record, Mozilla's behaviour is way more advanced than Hyatt describes.

Mozilla will check to see if the document contains any CSS, XSLT, or content from any namespace that is known (such as XHTML, MathML, etc -- basically anything with a frame constructor, IIRC).

If so, the document is assumed to be styled, and is then treated as normal XML+CSS or XML+XSLT.

If not, then the document is assumed to be unstyled pure XML and is rendered using a tree view similar too IE's.

HOWEVER, unlike IE, the DOM of the document is not changed, and if at any point the DOM is modified, then the page immediately switches back to XML+CSS mode.

In other words, Mozilla does The Cool Thing with XML.

Posted by Ian Hickson at February 14, 2003 5:48 AM

Is XML support, other than displaying of XML also planned. Like handling XML (like Mozilla's XMLHttpRequest and DOMDocument objects?).

But xForms should come in handy as well..

Posted by Doeke at February 14, 2003 9:26 AM

I don't believe that the failure to load devedge.netscape.com (I filed that bug already) has anything to do with XML support. The only issue
I've had with the non-rendering of XML happens
when the XML DOCTYPE is missing or mangled. So
if you take a look at http://www.w3c.org/Style/styling-XML
you will find that none of the XML examples there load.
Arguably, they should do something, but despite appearing on a w3c.org site they are pretty non-conformant.

Posted by Jonathan King at February 14, 2003 10:22 AM

I am a novice web designer and a VERY novice MT user. I have been playing around with the bookmarklets in MT. They seem to work very well in IE and make it really easy for non-computer users to make an entry in a blog, but the bookmarklets don't work at all in Safari. Does any one know what the problem is? Is it that Safari doesn't support Java in its bookmarks or something? I know this is off topic, but I figured that someone here would know the answer.

Posted by Chad Brantly at February 14, 2003 9:56 PM

Chad:

In order to get the MT-Bookmarklet work without the text selection function you have to delete the following piece of code in your bookmarklet:

?d.selection.createRange().text:d.getSelection()

-> Taken from the first result here:
http://www.google.com/search?q=movable+type+bookmarklet+safari

Posted by Mr Helpful at February 16, 2003 9:15 AM

I don't see any mention of XSLT. What are your plans for that?

Posted by Richard Tobin at February 17, 2003 3:17 PM

I will say that one of the nice things about the way IE handles XML is its ability to help me debug XML code. Both Netscape and Safari simply render the XML (even if they contain XML errors), for me IE is a great tool for debugging because it will choke on an error instead of ignoring it.

-Wayne

Posted by Wayne Brissette at February 18, 2003 11:42 AM

Does Safari (and KHTML) send "application/xhtml+xml" in its Accept: header yet? And does application/xhtml+xml invoke the XML parser, and not the Tag Soup parser?

Posted by red_one at February 19, 2003 10:57 PM