RE: several messages

> -----Original Message-----
> From: Ian Hickson []

> On Tue, 26 Jun 2001, Manos Batsis wrote:

> > It's logical to ignore the CSS if the XSLT is preferred in the
> > situation (as a web browser)
> Some people may prefer the opposite (CSS if available, otherwise
> XSLT). Document order may help with this. However the problem is
> bigger than that, as I described.

 I am not sure whether I have to argue with that or not. In general, I
think that if a user does not want to have the XSLT applied it's his
problem (at least if the document author wants the source document to be
transformed) and the custom solution should probably be in his client,
allowing him to choose with a prompt and radio buttons to choose like:

'Stylesheets specified:
 e.whatever (custom extension)'


   1)Apply		2)Accept default		3)Close

What I want to say is, the problem is complicated already, so including
'what the user might want' in the authors' implementation is impossible.
How am I supposed to know if a client is geeky enough and wants to see
my markup css styled only?

The only case I could imagine was a hypothetical situation where I
simulated XHTML rendering in XML documents using CSS. Even here, I don't
need xsl. If I did, the css would be linked by the result tree and not
the original document.

From the author's point of view now, I started working on a web based
XML editor some days ago. I found out that, I needed to use css in
editing mode while using XSL for various stages, but even with this
case, there was no real conflict between the two stylesheets, meaning
that, if you have a functionality in mind where two or more types of
style are useful, it always involves scripting (or some kind of
programmatic approach) and that's the layer that should take care of


> Finally, imagine that in the context of the following document:
>    <baz/>
> ...the following script is executed:
>    document.insertBefore(
>       document.createProcessingInstruction('xml-stylesheet', 
> 'href="a"'),
>       document.documentElement);
> ...if "a" is sent back as "text/xsl". What happens to the DOM? What
> happens to the document as far as the user is concerned?

I believe that the XSL transformation should immediately take place
changing the DOM according to the result tree. I see no problem here, am
I missing something?

Kindest regards,


Received on Wednesday, 27 June 2001 05:31:32 UTC