[Bug 17976] xml-stylesheet with type=text/xsl needs to be handled explicitly

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17976

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
>From bug 14689 comment 32:
> >
> > testing what happens when the XML file or the XSL file (or both)
> > are malformed
> 
> I can easily transform any or all of the tests already attached here to be
> ill-formed in those ways, but I have no idea what kind of result report you
> would need

I need to know things like (in no particular order):

- Does the XSL file get applied at all if it is a slow-loaded XSL file that is
ill-formed at the end?
- Does an XSL file that is ill-formed at the start delay the load event for the
entire time that the file is loading? (Or is the load canceled early maybe?)
- What is the processing model for an XSL file in general? Does it prevent
<script> execution in the parser after the <link> or <?xml-stylesheet> PI?
- What events fire? 'load'? 'DOMContentLoaded'?
- What is the .URL of the post-transformation Document?
- What DOM gets transformed if a script is mutating the Document that
references the XSL sheet?
- What happens if XSL sheet <link> references are added dynamically?
- What happens if a <link> is enabled or disabled dynamically?
- What if they're removed dynamically?
- Everything in note #8 above.
- Everything in comment 1 above. In particular, why is this HTML-specific?

Basically, what is the processing model. When does the transformation happen?
What happens before and after? What should the spec say. I know nothing of XSL,
so I'm not in a good position to answer these questions.


> > testing what happens with various MIME types for the XSL file
> 
> Can you point me to a parallel set of tests for xml-stylesheet
> type='text/css' so I can see how you expect this to be done?

An old set of CSS import tests I wrote years ago is here:

   http://www.hixie.ch/tests/evil/css/import/

(Note that many of these tests aren't valid anymore, but they should give you
some ideas.) This is a very simple set of tests, though, and not representative
of what we need. In particular, they do very little (if any) scripted DOM
testing, which is a prerequisite now.

The tests at http://www.w3.org/XML/2011/11/ssTests/ aren't very useful; they
aren't really tests, more demos, and they only seem to look at the most basic
of things (e.g. no scripting that I could see, nothing that would really show
what the processing model was).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 31 October 2012 22:42:49 UTC