There are some funny security reasons in Google Chrome for not allowing 
the document() function in XSLT only when executed from Javascript.

This test case works with Firefox and Internet Explorer (there is an 
issue with Edge...) and does not work with Opera (WebKit too...).

Issues in XSLT support are the main reasons for me to write XSLTForms 2 
without the necessity for XSLT!

--Alain

Le 02/07/2016 à 18:42, C. M. Sperberg-McQueen a écrit :
> On Jun 18, 2016, at 1:44 PM, Alain Couthures wrote:
>
>> Michael,
>>
>> Subforms are loaded with the load action so any event can trigger it. If
>> not, this would be an issue and I would be happy to have a test case if
>> this happens.
>> ...
>>
>> There is also the xf:include/@src control, which is an extension, just
>> to include an external file at the XSLT step.
> I have found xf:include very useful, and I find myself wanting to use
> it frequently.  But I have run into one difficulty.
>
> I have the impression that xf:include works in the main form,
> and in XML documents included by means of xf:include, but not in
> subforms.   The example at [1] illustrates what I mean:  when books.xml
> is loaded as a main form, it includes (via xf:include) a paragraph
> saying how many books it is displaying; when the same form is
> loaded as a subform, this information does not appear.
>
> [1] http://blackmesatech.com/2016/06/subformstest/include-test.xhtml
>
> Is this a bug or a design feature?
>
> Michael
>


------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Xsltforms-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Reply via email to