On May 8, 2014, at 8:31 AM, C. M. Sperberg-McQueen wrote:
> ...
> 
> When I click on the Show Books button for Camus, however, 
> instead of the list of his books I see what looks like the end of
> an XML comment ("xsltforms-subform-1 -->"), ...

Inserting alert() calls into xsltforms.js, it appears that line 9895
of xsltforms.js is assigning the following string to the innerHTML
property of the target xf:group element:

<!-- xsltforms-subform-0 --></body></html> xsltforms-subform-0 -->

My guess, after more tracing, is that xsltforms.xsl has been modified 
to insert one more XsltForms_MagicSeparator string, and so the 
references to the array of parts of the loaded subform are (some 
of them) off by one.

If I change the reference to sp[4] in line 9888 to refer instead to
sp[3], I get a more plausible-looking value assigned to innerHTML 
(reformatted for legibility):

<!-- xsltforms-subform-0 -->
<div xmlns="" 
     id="xsltforms-subform-0-repeat-0" 
     class="xforms-disabled xforms-repeat">
  <div class="xforms-repeat-item">
    <span xmlns="http://www.w3.org/1999/xhtml";
          id="xsltforms-subform-0-output-0"
          class="xforms-disabled xforms-control xforms-output 
xforms-appearance-minimal">
      <span class="value">
        <span class="xforms-value">&nbsp;</span>
      </span>
      <span class="xforms-alert">
        <span class="xforms-alert-icon">&nbsp;</span>
      </span>
    </span>
    - 
    <span xmlns="http://www.w3.org/1999/xhtml"; 
          id="xsltforms-subform-0-output-1"
          class="xforms-disabled xforms-control xforms-output 
xforms-appearance-minimal">
      <span class="value">
        <span class="xforms-value">&nbsp;</span>
      </span>
      <span class="xforms-alert">
        <span class="xforms-alert-icon">&nbsp;</span>
      </span>
    </span>
  </div>
</div>
<div id="xsltforms_console">&nbsp;</div>
<div id="statusPanel">... Loading ...&nbsp;</div>
<!-- xsltforms-subform-0 -->

But I regret to see that the subform itself still does not become
visible, which means that there is more to it than sp[4] becoming
sp[3].

Similar code seems to occur in the handling of components, by
the way, which means they also may need attention.
-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************





------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Xsltforms-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Reply via email to