RESOLVED FIXED 19206
<?xml-stylesheet is totally broken in Safari 
https://bugs.webkit.org/show_bug.cgi?id=19206
Summary <?xml-stylesheet is totally broken in Safari
Laurens Holst
Reported 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
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 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.
Laurens Holst
Comment 2 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
Alexey Proskuryakov
Comment 3 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.
Laurens Holst
Comment 4 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...
Alexey Proskuryakov
Comment 5 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.
Laurens Holst
Comment 6 2008-09-03 09:01:50 PDT
Okay, thank you, just making sure :). I hope they will update their codebases soon!
Note You need to log in before you can comment on or make changes to this bug.