zoukankan      html  css  js  c++  java
  • Result of Transforming XML by XSLT in Different Browsers

    Generally most of the browsers transform XMLs in 2 ways, I mean two kinds of APIs

    For IE serial browsers, we got

    xml.transformNode(xsl)

    It's pretty easy, but the disadvantage is that the result is pure text.

    Another way is supported by Mozilla, Opera, and Safari serial browsers

    var processor = new XSLTProcessor();
    processor.importStylesheet(xsl);
    var result = processor.transformToDocument(xml);

    It returns a document as result, that's better than IE. The problem for these browsers is, the transform result from XSLT is expected to be ONE element. Which means the following kind of result is incorrect.

    <div>...</div><div>...</div>

    Because they are 2 elements.

    In this situation, Firefox handle it in the way that wrap the result with a <transformiix:result /> tag. Whild Safari will show an error message (TOO bad).

    To solve the problem, wrap the result with another tag like

    <div>
      <div>...</div>  <div>...</div> </div>

     Or another way

    var result =processor.transformToFragment(xml, xml);

     For detail information of these APIs, go to the following link:

    http://developer.mozilla.org/cn/docs/Using_the_Mozilla_JavaScript_interface_to_XSL_Transformations

    Although non-IE serial browsers returns DOM element for us, we can not take the advantage of it because of cross-browser issues. Instead, we have to serialize the element into a string, and then we can deal with it in the same way as IE.

    var xmls = new XMLSerializer();
    var html = xmls.serializeToString(result);

    (Tested in IE6, FF2, Safari3)

  • 相关阅读:
    子程序定义-3
    子程序定义-2
    子程序定义-1
    MQ报 AMQ9259
    观nginx与lvs负载均衡的较量
    绑定变量值长度不一致,mismatch问题
    perl-printf 函数
    perl 运算符
    强制让SQL走谓词推入
    PGA概念
  • 原文地址:https://www.cnblogs.com/yaoxing/p/2179663.html
Copyright © 2011-2022 走看看