RE: [xsl] Any samples of client-side XSLT to generate webpages?

Subject: RE: [xsl] Any samples of client-side XSLT to generate webpages?
From: "Daniel Joshua" <daniel.joshua@xxxxxxxxxxxx>
Date: Tue, 27 Jul 2004 17:44:55 +0800
Ok, I understand this now.

If I ever need to produce HTML fragments I will use Sarissa (I find how it
works very intersting). But the approach I am currently trying is to produce
whole HTML pages by XSLT transformation in the client's browser.

Can anyone explain to me why the below happens:
  - work in IE only
  - unable to submit for in Mozilla
  - works in Mozilla - currently need to manually add the '?transform=true',
but I might automate this later)
  - nothing visible (except background graphic) in IE

I really need help. This is so confusing to me.


-----Original Message-----
From: Marcus Andersson [mailto:marcus@xxxxxxxxxx]
Sent: Tuesday, 27 July, 2004 4:05 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Any samples of client-side XSLT to generate webpages?

Daniel Joshua wrote:

>   document.getElementById("appendChild")
>   .appendChild(document.importNode(resultDoc.documentElement, true));
> it lookes like you are add a whole document into a the "appendChild"
> element, is that legal or am I mistaken?
It's perfectly legal the way it's done (from a node perspective). But it
doesn't enforce that the usage is
correct (ie you can create a complete html document with html-head-body etc
with your transform and it would
be incorrect (from a DTD point of view) if you added that to a div in your
document, but if you produce a
document that has for example a div as it's root element then it's perfectly
legal). You mostly use Sarissa
(and approaches similar to Sarissa) to produce HTML fragments and not
complete HTML documents (unless you want
to overwrite a complete document with the result, this is done for example
if you opens a window or iframe on
the client and want to populate it from scratch). At least I do.


Current Thread