Bug 19206 - <?xml-stylesheet is totally broken in Safari
Summary: <?xml-stylesheet is totally broken in Safari
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 525.x (Safari 3.1)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL: http://www.grauw.nl/
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-23 02:48 PDT by Laurens Holst
Modified: 2008-09-03 09:01 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Laurens Holst 2008-05-23 02:48:38 PDT 
Hi,

Using <?xml-stylesheet in an XHTML document used to work in Safari. However, at some point during the 3 line, this stopped working, particularly the alternate="yes" and media="print" ‘attributes’ on the processing instruction seem to be ignored, and all styles are applied at once.

You can see this having a devastating effect on my website, which has been the case for some time now, making it effectively inaccessible for Safari users.

~Grauw
Comment 1 Alexey Proskuryakov 2008-05-23 06:16:26 PDT 
I see the problem with shipping Safari 3.1.1, but the site works OK with a nightly build. This was fixed in bug 17129 and bug 11939.

It does not look like media and alternate ever worked in shipping Safari/WebKit.
Comment 2 Laurens Holst 2008-05-23 06:19:57 PDT 
Great to hear.

I remember testing on my grandfather’s Mac. Maybe it wasn’t served as application/xhtml+xml back then? It does this based on the Accept header, and when served as text/html it has the stylesheets as links inside the head element.

~Grauw
Comment 3 Alexey Proskuryakov 2008-05-23 06:29:57 PDT 
Yes, this explains it coompletely - we did change our Accept header to include application/xhtml+xml in Safari 3, see bug 9572.
Comment 4 Laurens Holst 2008-09-03 04:28:50 PDT 
Are you sure this is fixed? My website still looks broken in Safari 3.1.2 and Google Chrome...
Comment 5 Alexey Proskuryakov 2008-09-03 08:37:49 PDT 
Please try a nightly build from <http://nightly.webkit.org> - the fix is not yet released with Safari. I don't know for sure why this site doesn't work with Chrome - it's based on a rather dated version of WebKit, so it's possible that it doesn't include these fixes either.
Comment 6 Laurens Holst 2008-09-03 09:01:50 PDT 
Okay, thank you, just making sure :). I hope they will update their codebases soon!