Safari won't display XML content with an embedded stylesheet

Question

Level 1

0 points

Safari won't display XML content with an embedded stylesheet

I'm using Safari 5.0.2 on Windows XP. I cannot get it to display an XML document with an embedded CSS stylesheet. The file in question appears in this ZIP file: http://www.hl7.org/documentcenter/ballots/2011JAN/downloads/CDAR2IG_SDISP_R1_D12011JAN.zip

That document demonstrates is an attempt to enable display of standardized healthcare content in common web browsers. Can anyone here help?

Dell, Windows XP Pro

Posted on Dec 1, 2010 7:40 PM

Reply

Answer 1

b noir

Level 9

72,336 points

Dec 1, 2010 8:50 PM in response to KWBoone

My Chrome is also having trouble displaying that file properly.

I tried running the source of the file through the W3C CSS validator at:

http://jigsaw.w3.org/css-validator/#validatebyinput

It returned:

Parse Error Lexical error at line 1, column 2. Encountered: "?" (63), after : "<"</div>

... but I'm not a web developer, so my advice about coding has to be taken with a rather large grain of salt.

Reply

Answer 2

KWBoone Author

Level 1

0 points

Dec 1, 2010 9:03 PM in response to b noir

I have a separate bug report to Chrome on this one, same general result in display. The file is an XML document, not a CSS style-sheet. It contains an xml-stylesheet processing instruction that has a local URI #hl7-css-for-cda pointing to an element in the XML that contains the CSS stylesheet. That element uses xml:id to identify itself, so it is (according to the W3C) possible for the browser to determine that element as being the target of the URI.

The problem appears to be that the Display Engine in Safari won't load the content of that URI as a CSS stylesheet.

When I validate the CSS content in that XML element it returns as being valid CSS, and when I validate the XML using my XML editor, it is both well formed, and valid against the XML Schema appropriate to that file.

Reply

Answer 3

b noir

Level 9

72,336 points

Dec 1, 2010 9:24 PM in response to KWBoone

Given that both Chrome and Safari are getting this (and they are both WebKit-based), it might also be worth writing up a bug for the WebKit folks:

http://webkit.org/quality/reporting.html

Have you also submitted a bug to Apple? If you want to track the report, first you'd need to sign up as a developer (for free):

http://developer.apple.com/programs/register/

... and then you can use the Apple Bug reporter:

http://developer.apple.com/bugreporter/

Reply

Answer 4

KWBoone Author

Level 1

0 points

Dec 1, 2010 9:27 PM in response to b noir

Thanks for the links for WebKit and Apple, I will submit it there and to Apple.

Reply

Answer 5

b noir

Level 9

72,336 points

Dec 1, 2010 9:48 PM in response to KWBoone

🙂 No problem. Fingers crossed in New Zealand that the various reports bring you some joy with getting the issue resolved.

Reply