Comment by bryanrasmussen

I tried to comment on this just now but I was blocked as the thread has been limited to collaborators, their word not mine, but wow.

So I guess I'll put it here assuming someone reads.

Given the various comments people have about the dependencies on XSLT that various standards, applications and workflows have. I believe that the default display of XML documents in Chrome, Firefox, and I suppose Edge is handled by an XSLT.

It used to be that MSXML shipped with an XSLT (and even earlier a wd-xsl document) as a resource that was used to style any XML document for display if the XML document did not have an associated stylesheet when you opened it in IE or other views that used IE for rendering.

I believe this same thing is done by the browsers mentioned, or at least it used to be

https://stackoverflow.com/questions/9463402/default-xml-styl...

which is why when you open an XML document without styling information in those documents it is represented as a tree view with expandable collapsible nodes.

I suppose they will just implement a default rendering for XML using some other code rather than running an XSLT upon it, but this applies as well as all these edge cases of handling RSS feeds etc.

Safari does not have a stylesheet rendering for unstyled XML which is why it just shows the text nodes of the document and nothing else.