[whatwg] Client-side includes proposal

[Kristof Zelechovski]

I have not bumped into any XSLT-related browser problems except for
converting resource tree fragments to nodes which is unportable but it is
needed in advanced applications only where you need recursion on document
node construction.  Anyway, my plan is to make the transformation a part of
the publishing process, not a part of the rendering process; that is, you
use your reliable XSLT driver to do the transformation and publish the
result to the server.  Clean, automatic and simple.
Chris

-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Shannon
Sent: Monday, August 18, 2008 7:57 PM
To: Kristof Zelechovski
Cc: 'WHAT working group'
Subject: Re: [whatwg] Client-side includes proposal

Kristof Zelechovski wrote:
> Client-side includes make a document transformation, something which
> logically belongs XSLT rather than HTML.  And what would the workaround
for
> legacy browsers be?
> Chris
>   

You make good points but last I checked general browser and editor 
support for XSLT was abysmal. Everyone is saying its on their "roadmaps" 
though so maybe it will one day be reliable enough to use.