ansaurus

Question

client side xslt with javascript in firefox

Answer 1

A:

Try

document.anchors = document.getElementsByTagName('a')
alert(document.anchors)

document.anchors is old but you might be able to work around the problem by assigning it as a property.

steamer25 2009-06-26 22:30:25

what do you think of this: if (!document.anchors) document.anchors = document.getElementsByTagName('a')

elcuco 2009-06-26 22:33:39

Yeah after re-reading and seeing that Rico has a bunch of existing JS, I agree. I'm not sure if you need to check first--might work fine in IE too if you just assign it ;) . If it does bust IE, your solution looks good.

steamer25 2009-06-26 22:37:50

I tried something just like this but I don't think it works. I replaced the script in the xsl with this<script type="text/javascript"> alert('document = ' + document); if (!document.anchors) document.anchors = document.getElementsByTagName('a'); alert('document.anchors =' + document.anchors);</script>In firefox i get 'document.anchors =[object HTMLCollection]'In IE i get 'document.anchors =[object]'If any of my existing js tries to access document.anchors i would imagine this would cause errors.This might work if i could somehow redeclare the entire document object.

2009-06-26 23:23:08

Answer 2

+3 A:

1) Fixing your problem

Solving your issue is as simple as changing value of the @method attribute from "xml" to "html" on xsl:output element.

2) Explaining the difference

HTML DOM extends core XML DOM interfaces. So, for example, the collection "forms" is not present in the XMLDocument, but is in HTMLDocument

Sergey Ilinsky 2009-06-27 11:00:45

Answer 3

A:

The reason I used xml was I wanted to use xhtml for the output. Since I am doing the transformations on the client side I am limited to xslt 1.0 and xhtml is not an option. I had seen on several sites that the way to output xhtml was to select xml and use the omit-xml-declaration. I guess this is what was causing firefox to create the xml DOM.

Following Sergey's advice I changed my output method around and everything seems to work. This is what it looks like now

  <xsl:output method="html"
  encoding="ISO-8859-1"
  indent="yes"
  doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
  doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/&gt;

I checked out the doctype in IE. It still says it is xhtml even though the method is html. I don't know why so many sites suggest the xml output method hack...

Thanks for explaining the difference with the xml and html DOMs. Out of curiosity, is there any way to manually create a html dom from the xml dom?

2009-06-29 14:24:16

I could not bump up Sergey's post or comment on it since i don't have enough rep. I had to create an answer to continue the discussion.

2009-06-29 14:25:50

ansaurus

tags:

views:

answers:

client side xslt with javascript in firefox

related questions