Robert Koberg wrote:
Your'e transformation does not need to take place on the client. It is
rather large for a client-side transform (the XSL and the source). The
transform makes Firefox freeze for a bit and takes a long time to load.
Nobody is forced to run it on the client. That FF "freezes" while
transforming is an issue with the FF implementation; compare for
instance with IE.
And google won't index it (?)
Which is kind of sad. But for now, I'd be already happy if Google would
start indexing XHTML (when served with an XHTML media type).
Hm. I think my XSLT needs document only in a few special cases (such as,
for instance,
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-latest.xml>),
where it *seems* to work.
The problem that I see over here is that the HTML transformation result
appears without CSS styling applied.
I see it there too.
It could have something to do with the size of the transformation. The
XSL weighs in at 5000+ lines and 190K, and the source is largish. Have
you tried with a small/simple sample to see if styling works there?
No.
But it used to work a few months ago (before Opera introduced the
*other* bug causing the transformation to abort entirely).
<http://greenbytes.de/tech/webdav/rfc4770.xml> is smaller (just 16K),
but fails the same way, BTW.
BR, Julian
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--