xsltforms-support — XSLTForms support list

[Xsltforms-support] Issue with deleting items from repeat list

[Mats E. <mat...@li...>]

Hi Alan,

By chance stumbled upon a potential bug in the xsltforms library recently. The attached simple test case shows how an exception is thrown when user clicks Delete trigger on the last item in a repeat list. Only in Chrome it seems.

It is possible to avoid the exception by putting an extra null check in the if() statement on the line where the exception is thrown, however, it looks like the issue may reveal a deeper issue, whose effects could sometimes be more subtle.

/ Mats

Re: [Xsltforms-support] Multimodel forms

[Tim T. <tim...@gm...>]

The form is working now. I was trying to dispatch an event to a control
upon "xforms-model-construct-done" rather than "xforms-ready," which
obviously wouldn't work!

Tim

On Wed, Aug 30, 2017 at 7:25 PM, Tim Thompson <tim...@gm...> wrote:

> Hello,
>
> I have a (theoretical) XForms instance with a set of unit tests that I
> would like to run using the @iterate attribute. With a single model, this
> seems to work, but I would like to create a more modular form containing a
> main model and a test model. With two models, I am no longer able to
> dispatch an event to trigger the iteration.
>
> Here is an example (nonworking) form with two models:
>
> https://bibfram.es/basex/budgeting/multimodel.xhtml
>
> Is there a better way to achieve what I'm trying to accomplish?
>
> Thanks in advance,
> Tim
>
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>

[Xsltforms-support] Multimodel forms

[Tim T. <tim...@gm...>]

Hello,

I have a (theoretical) XForms instance with a set of unit tests that I
would like to run using the @iterate attribute. With a single model, this
seems to work, but I would like to create a more modular form containing a
main model and a test model. With two models, I am no longer able to
dispatch an event to trigger the iteration.

Here is an example (nonworking) form with two models:

https://bibfram.es/basex/budgeting/multimodel.xhtml

Is there a better way to achieve what I'm trying to accomplish?

Thanks in advance,
Tim



--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

Re: [Xsltforms-support] XForms unit testing

[Alain C. <ala...@ag...>]

Hello,

First, XForms unit testing requires extra actions to interact with controls just as users would do: click somewhere, select an item in a drop-down list, press a key,…

Then, for checking the form rendering, accessing the DOM sounds the best approach. I have already tested this with Fleur as a substitute for XQIB because it allows, using the b:dom() function, to evaluate XPath expressions directly on the current page content.

Yet, it might be tricky to write XPath expressions dealing with extra HTML elements added for XForms controls and getting properties from an XForms control with XPath is to be specified too…

Implementing extra actions for assertions sounds great!

All this would be a wonderful task for the XForms Users Group, especially regarding to the new Test Suite to be written for XForms 2.0!

What do you think?

--Alain

De : Tim Thompson
Envoyé le :jeudi 20 juillet 2017 16:02
À : xsl...@li...
Objet :[Xsltforms-support] XForms unit testing

Hello,
Michael's recent question spurred me to ask a lingering one that I have had: namely, has anyone developed an approach to unit testing XForms applications, specifically in XSLTForms?
I know of Eric van der Vlist's XForms Unit project (http://xformsunit.org/), which I believe uses the Orbeon Form Runner as its testing environment, but the project doesn't seem to be under active development.
I'm interested in finding a simple approach to testing in XSLTForms. Perhaps some custom actions could be defined to implement standard testing functions such as assert, assert-equals, etc.?
Best regards,
Tim



--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

On Wed, Jul 19, 2017 at 9:21 AM, Alain Couthures <ala...@ag...> wrote:
The path for itemset has to be written relative to the one of the select: in your test case, just add "../../" at the beginning if you want to keep it relative.
--Alain

De : C. M. Sperberg-McQueen
Envoyé : ‎18/‎07/‎2017 20:51
À : xsl...@li...
Cc : C. M. Sperberg-McQueen
Objet : [Xsltforms-support] select1, itemset,value (what is this form doing wrong?)
Trying to implement a new functionality I thought would be simple,
I am running into unexpected difficulties with the xf:select widget.

I have put a sample form at

http://www.blackmesatech.com/2017/07/testcase/index.xml

Several problems are arising:

- First and foremost, the menu displayed by the following widget
appears to be empty of text, although xf:output statements inserted
for diagnostic purposes appear to show that the XPath expressions
used are correct.

    <xf:select ref="p[@id='select']/@items">
      <xf:itemset nodeset="list/item">
<xf:label ref="."/>
<xf:value ref="@id"/>
      </xf:itemset>
    </xf:select>

- Second, when I try to use xf:output in the xf:label element, 
I get an error; ditto when I try to use a constant but remove the @ref
binding attribute.  Are both the value and the label of an itemset
required to use @ref?

Anyone who can shed any light on this would receive a large shipment
of gratitude (and a beer if we’re ever in the same bar).

best,

Michael Sperberg-McQueen


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] XForms unit testing

[Tim T. <tim...@gm...>]

Hello,

Michael's recent question spurred me to ask a lingering one that I have
had: namely, has anyone developed an approach to unit testing XForms
applications, specifically in XSLTForms?

I know of Eric van der Vlist's XForms Unit project (http://xformsunit.org/),
which I believe uses the Orbeon Form Runner as its testing environment, but
the project doesn't seem to be under active development.

I'm interested in finding a simple approach to testing in XSLTForms.
Perhaps some custom actions could be defined to implement standard testing
functions such as assert, assert-equals, etc.?

Best regards,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library


On Wed, Jul 19, 2017 at 9:21 AM, Alain Couthures <
ala...@ag...> wrote:

> The path for itemset has to be written relative to the one of the select:
> in your test case, just add "../../" at the beginning if you want to keep
> it relative.
> --Alain
> ------------------------------
> De : C. M. Sperberg-McQueen <cm...@bl...>
> Envoyé : ‎18/‎07/‎2017 20:51
> À : xsl...@li...
> Cc : C. M. Sperberg-McQueen <cm...@bl...>
> Objet : [Xsltforms-support] select1, itemset,value (what is this form
> doing wrong?)
>
> Trying to implement a new functionality I thought would be simple,
> I am running into unexpected difficulties with the xf:select widget.
>
> I have put a sample form at
>
> http://www.blackmesatech.com/2017/07/testcase/index.xml
>
> Several problems are arising:
>
> - First and foremost, the menu displayed by the following widget
> appears to be empty of text, although xf:output statements inserted
> for diagnostic purposes appear to show that the XPath expressions
> used are correct.
>
>     <xf:select ref="p[@id='select']/@items">
>       <xf:itemset nodeset="list/item">
> <xf:label ref="."/>
> <xf:value ref="@id"/>
>       </xf:itemset>
>     </xf:select>
>
> - Second, when I try to use xf:output in the xf:label element,
> I get an error; ditto when I try to use a constant but remove the @ref
> binding attribute.  Are both the value and the label of an itemset
> required to use @ref?
>
> Anyone who can shed any light on this would receive a large shipment
> of gratitude (and a beer if we’re ever in the same bar).
>
> best,
>
> Michael Sperberg-McQueen
>
>
> ********************************************
> C. M. Sperberg-McQueen
> Black Mesa Technologies LLC
> cm...@bl...
> http://www.blackmesatech.com
> ********************************************
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

Re: [Xsltforms-support] solved (was: Re: select1, itemset, value (what is this form doing wrong?))

[Steven P. <ste...@cw...>]

On Tue, 18 Jul 2017 10:58:58 +0200, C. M. Sperberg-McQueen  
<cm...@bl...> wrote:

> The problem here is so simple it’s slightly embarrassing:  the ‘ref’
> attribute on xf:select sets the context item, so the relative expression
> in the xf:itemset/@nodeset attribute cannot (as written) succeed:  no
> attribute every has element children.  If one makes it absolute
> (lead with instance(‘name’)/… or with ../../), the drop down menu
> ceases to be empty.

Just as a reminder for everyone, if you have a @ref on a control (which as  
Michael points out resets the context), and you have a nested expression  
that you want to be relative to the same thing the ref was relative to  
before resetting the context, there is a solution: the context() function.

This function gives you the context used for the ref, while "." gives you  
the context produced by the ref.

Example:

     <select ref="p[@id='select']/@items">
       <itemset ref="list/item">

the itemset would try to reference "p[@id='select']/@items/list/item"  
(obviously empty).

     <select ref="p[@id='select']/@items">
       <itemset ref="context()/list/item">

would be evaluated in the same contact as the ref on <select>.

You can see another example of context() being used in this example:
    http://homepages.cwi.nl/~steven/forms/examples/data-driven/

>> - Second, when I try to use xf:output in the xf:label element,
>> I get an error; ditto when I try to use a constant but remove the @ref
>> binding attribute.  Are both the value and the label of an itemset
>> required to use @ref?
>
> For this I have currently found no simple solution.

This may help:

   <repeat ref="*">
      <input ref=".[count(*)=0]"><label><output value="concat(name(.), ':  
')"/></label></input>
      <output value="if(count(*)=0, '', concat(name(.), ': '))"/>
      <repeat ref="@*" class="inline">
        <input ref="."><label><output value="concat('@', name(.),  
'=')"/></label></input>
      </repeat>

     **NEST HERE**

   </repeat>

At the point **NEST HERE** you just copy and paste the whole repeat again;  
do this as many times as needed to match the maximum depth of elements in  
the instance you have.

In your case you need outputs not inputs, so just replace all <input>s  
with <output>s.

You can see it working at  
http://homepages.cwi.nl/~steven/forms/examples/data-driven/edit.xml

It takes any random XML instance, and allows you to edit it (up to a  
maximum depth).

Hope this helps.

Steven

Re: [Xsltforms-support] select1, itemset, value (what is this form doing wrong?)

[Alain C. <ala...@ag...>]

The path for itemset has to be written relative to the one of the select: in your test case, just add "../../" at the beginning if you want to keep it relative.
--Alain

-----Message d'origine-----
De : "C. M. Sperberg-McQueen" <cm...@bl...>
Envoyé : ‎18/‎07/‎2017 20:51
À : "xsl...@li..." <xsl...@li...>
Cc : "C. M. Sperberg-McQueen" <cm...@bl...>
Objet : [Xsltforms-support] select1, itemset,value (what is this form doing wrong?)

Trying to implement a new functionality I thought would be simple,
I am running into unexpected difficulties with the xf:select widget.

I have put a sample form at

http://www.blackmesatech.com/2017/07/testcase/index.xml

Several problems are arising:

- First and foremost, the menu displayed by the following widget
appears to be empty of text, although xf:output statements inserted
for diagnostic purposes appear to show that the XPath expressions
used are correct.

    <xf:select ref="p[@id='select']/@items">
      <xf:itemset nodeset="list/item">
	<xf:label ref="."/>
	<xf:value ref="@id"/>
      </xf:itemset>
    </xf:select>

- Second, when I try to use xf:output in the xf:label element, 
I get an error; ditto when I try to use a constant but remove the @ref
binding attribute.  Are both the value and the label of an itemset
required to use @ref?

Anyone who can shed any light on this would receive a large shipment
of gratitude (and a beer if we’re ever in the same bar).

best,

Michael Sperberg-McQueen


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] select1, itemset, value (what is this form doing wrong?)

[Tim T. <tim...@gm...>]

Michael,

I wish I could be of help, but this does seem to be a bug. I remember
running into the same issue previously.

Would it work, for your application, to define an <xf:bind
id="labelBinding" nodeset="..." calculate="..." /> with more complex
conditional logic to generate your itemset labels?

Best wishes,
Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library


On Tue, Jul 18, 2017 at 3:06 AM, C. M. Sperberg-McQueen <
cm...@bl...> wrote:

>
> > On Jul 18, 2017, at 8:48 AM, C. M. Sperberg-McQueen <
> cm...@bl...> wrote:
> >
> > Trying to implement a new functionality I thought would be simple,
> > I am running into unexpected difficulties with the xf:select widget.
> >
> > I have put a sample form at
> >
> > http://www.blackmesatech.com/2017/07/testcase/index.xml
> >
>
> Two other samples in the same directory (test2.xml, test3.xml)
> illustrate simple variations (child elements instead of attributes,
> and similar) and exhibit similar non-optimal behavior.
>
> ********************************************
> C. M. Sperberg-McQueen
> Black Mesa Technologies LLC
> cm...@bl...
> http://www.blackmesatech.com
> ********************************************
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] select1, itemset, value (what is this form doing wrong?)

[C. M. Sperberg-M. <cm...@bl...>]

Trying to implement a new functionality I thought would be simple,
I am running into unexpected difficulties with the xf:select widget.

I have put a sample form at

http://www.blackmesatech.com/2017/07/testcase/index.xml

Several problems are arising:

- First and foremost, the menu displayed by the following widget
appears to be empty of text, although xf:output statements inserted
for diagnostic purposes appear to show that the XPath expressions
used are correct.

    <xf:select ref="p[@id='select']/@items">
      <xf:itemset nodeset="list/item">
	<xf:label ref="."/>
	<xf:value ref="@id"/>
      </xf:itemset>
    </xf:select>

- Second, when I try to use xf:output in the xf:label element, 
I get an error; ditto when I try to use a constant but remove the @ref
binding attribute.  Are both the value and the label of an itemset
required to use @ref?

Anyone who can shed any light on this would receive a large shipment
of gratitude (and a beer if we’re ever in the same bar).

best,

Michael Sperberg-McQueen


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************

[Xsltforms-support] solved (was: Re: select1, itemset, value (what is this form doing wrong?))

[C. M. Sperberg-M. <cm...@bl...>]

> On Jul 18, 2017, at 8:48 AM, C. M. Sperberg-McQueen <cm...@bl...> wrote:
> 
> Trying to implement a new functionality I thought would be simple,
> I am running into unexpected difficulties with the xf:select widget.
> 
> I have put a sample form at
> 
> http://www.blackmesatech.com/2017/07/testcase/index.xml
> 
> Several problems are arising:
> 
> - First and foremost, the menu displayed by the following widget
> appears to be empty of text, although xf:output statements inserted
> for diagnostic purposes appear to show that the XPath expressions
> used are correct.
> 
>    <xf:select ref="p[@id='select']/@items">
>      <xf:itemset nodeset="list/item">
> 	<xf:label ref="."/>
> 	<xf:value ref="@id"/>
>      </xf:itemset>
>    </xf:select>

The problem here is so simple it’s slightly embarrassing:  the ‘ref’
attribute on xf:select sets the context item, so the relative expression
in the xf:itemset/@nodeset attribute cannot (as written) succeed:  no
attribute every has element children.  If one makes it absolute
(lead with instance(‘name’)/… or with ../../), the drop down menu
ceases to be empty.

So the belief that the diagnostic messages showed the XPath expressions
to be correct was wrong:  the two instances of the same expression
had different context nodes.  

I can now shift to the challenge of making the display nicer.

> - Second, when I try to use xf:output in the xf:label element, 
> I get an error; ditto when I try to use a constant but remove the @ref
> binding attribute.  Are both the value and the label of an itemset
> required to use @ref?

For this I have currently found no simple solution.  

Binding to a node using @ref works great when there is a node whose
string value is what you want in the menu.  That’s not the case for the
application I’m working on:  the items from which the user must select 
often have child elements, some of which should be included in the value 
to be shown in the menu and others of which [the end-notes] should be 
omitted.  And for some entries additional information should be supplied 
from context.  A simple ref attribute binding to the original element will 
produce the desired string perhaps 20 or 30 per cent fo the time.

Probably the best solution I can come up with in the next couple of hours
will be to apply an XSLT transform to the current instance data to create 
an auxiliary document instance containing the appropriate label and code
values.  In XSLTForms I can use the transform() function; in another XForms
implementation one would need to submit the current main instance to
a service on the server which would run the XSLT transform and return
the appropriate select-values instance.


> 
> Anyone who can shed any light on this would receive a large shipment
> of gratitude (and a beer if we’re ever in the same bar).

It’s too early in the day just now, but I’ll take myself up on this tonight.


********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************

Re: [Xsltforms-support] select1, itemset, value (what is this form doing wrong?)

[C. M. Sperberg-M. <cm...@bl...>]

> On Jul 18, 2017, at 8:48 AM, C. M. Sperberg-McQueen <cm...@bl...> wrote:
> 
> Trying to implement a new functionality I thought would be simple,
> I am running into unexpected difficulties with the xf:select widget.
> 
> I have put a sample form at
> 
> http://www.blackmesatech.com/2017/07/testcase/index.xml
> 

Two other samples in the same directory (test2.xml, test3.xml) 
illustrate simple variations (child elements instead of attributes,
and similar) and exhibit similar non-optimal behavior.  

********************************************
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
cm...@bl...
http://www.blackmesatech.com
********************************************

Re: [Xsltforms-support] Random firefox crashes

[Winona S. <wsa...@gm...>]

Thanks Tim!
Yes, we make heavy use of bootstrap, I think it really helps make the forms
a bit more user friendly, hopefully it is not a contributing factor to the
mysterious Firefox bugs.

I see you ended up changing your xf:select1 to use xf:copy, I will do some
additional testing and see if that resolves my issue. However I would
prefer to keep the xf:item/xf:value if possible (make it easier to
eventually use things like .odd files for controlled vocabulary).

-Winona






On Wed, May 10, 2017 at 12:17 PM, Tim Thompson <tim...@gm...> wrote:

> Hi, Winona,
>
> I recently had a similar issue with Firefox crashing (see this thread:
> https://sourceforge.net/p/xsltforms/mailman/message/35726489/). Mine
> seemed to be related to loading instance data into an xf:select1.
>
> By the way, nice form! Looks as though you've done a great job integrating
> XSLTForms with Bootstrap.
>
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> www.linkedin.com/in/timathompson
> tim...@ya...
>
> On Wed, May 10, 2017 at 10:57 AM, Winona Salesky <wsa...@gm...>
> wrote:
>
>> I am encountering some random crashes in Firefox with XForms. I can see
>> no patterns and am not even sure how to start diagnosing the issue. The
>> form works without a problem in Chrome and Safari and for a short time in
>> Firefox. There does not seem to be any action in particular that triggers
>> the crash.
>>
>> Linkt to problematic form:
>> http://wwwb.library.vanderbilt.edu/exist/apps/srophe-admin/
>> forms/form.xq?form=srophe/person.xml
>>
>> Any hints on how to get started debugging?
>> Thanks,
>> -Winona
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>

Re: [Xsltforms-support] Random firefox crashes

[Tim T. <tim...@gm...>]

Hi, Winona,

I recently had a similar issue with Firefox crashing (see this thread:
https://sourceforge.net/p/xsltforms/mailman/message/35726489/). Mine seemed
to be related to loading instance data into an xf:select1.

By the way, nice form! Looks as though you've done a great job integrating
XSLTForms with Bootstrap.

Tim


--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library

www.linkedin.com/in/timathompson
tim...@ya...

On Wed, May 10, 2017 at 10:57 AM, Winona Salesky <wsa...@gm...> wrote:

> I am encountering some random crashes in Firefox with XForms. I can see no
> patterns and am not even sure how to start diagnosing the issue. The form
> works without a problem in Chrome and Safari and for a short time in
> Firefox. There does not seem to be any action in particular that triggers
> the crash.
>
> Linkt to problematic form:
> http://wwwb.library.vanderbilt.edu/exist/apps/srophe-admin/forms/form.xq?
> form=srophe/person.xml
>
> Any hints on how to get started debugging?
> Thanks,
> -Winona
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

[Xsltforms-support] Random firefox crashes

[Winona S. <wsa...@gm...>]

I am encountering some random crashes in Firefox with XForms. I can see no
patterns and am not even sure how to start diagnosing the issue. The form
works without a problem in Chrome and Safari and for a short time in
Firefox. There does not seem to be any action in particular that triggers
the crash.

Linkt to problematic form:
http://wwwb.library.vanderbilt.edu/exist/apps/srophe-admin/forms/form.xq?form=srophe/person.xml

Any hints on how to get started debugging?
Thanks,
-Winona

Re: [Xsltforms-support] Question about show='new' in submission

[Alain C. <ala...@ag...>]

Hi Winona,

Sorry, could you please be more explicit about "downloading an instance 
without saving it"? Do you mean downloading at client-side and saving at 
server-side??

I really don't see why you have this problem with the browser window 
being forced to the top after activating a trigger. I have never heard 
about such a behavior before... Which revision of XSLTForms are you using?

--Alain

Le 26/04/17 à 15:25, Winona Salesky a écrit :
> Do you have any tips for downloading an instance without saving it?
>
> Also, I noticed in Firefox, Chrome and Safari when clicking on any 
> xf:trigger I get bounced to the top of the page, this causes some 
> grumbling among my users since they then have to scroll down to the 
> newly inserted element. I would think the expected behavior would be 
> to set the focus on the new element? Any chance this could be an 
> enhancement?
>
> Thanks,
> -Winona
>
>
> On Tue, Apr 25, 2017 at 3:40 PM, Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Hi Winona,
>
>     The Profiler is, itself, an XForms page. It uses an XPath
>     expression such as
>     "serialize(instance('view'),'application/xml','yes')" where the
>     third parameter is about indentation.
>
>     --Alain
>
>     Le 22/04/17 à 14:24, Winona Salesky a écrit :
>>     Yes disable the popup blocker did fix this. I think adding a try
>>     catch could be useful.
>>     Is there different way to allow users to view the XML instance
>>     data? For example, perhaps I could take advantage of some of the
>>     code that the profiler uses, but just isolate the instance
>>     information?
>>     Thanks for your help!
>>     -Winona
>>
>>
>>     On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures
>>     <ala...@ag...
>>     <mailto:ala...@ag...>> wrote:
>>
>>         Hi Winona,
>>
>>         I suspect that this issue is just due to pop-ups not being
>>         allowed.
>>
>>         The error about w.document is just after this instruction:
>>         var w = window.open("about:blank","_blank");
>>
>>         I should probably wrap this with a try-catch statement just
>>         to alert users about allowing popup. What do you think?
>>
>>         --Alain
>>
>>         Le 21/04/17 à 23:15, Winona Salesky a écrit :
>>>         Hi All,
>>>         I'm trying to open my instance in a new window, using a
>>>         submission with show='new' and am getting this error:
>>>
>>>         0 -> Dispatching event xforms-submit on <SPAN
>>>         class="xforms-submission" id="send"/>
>>>         0 -> Dispatching event xforms-submit-serialize on <SPAN
>>>         class="xforms-submission" id="send"/>
>>>         1 -> Submit post - application/xml - services/submit.xql - false
>>>         5 -> Dispatching event xforms-submit-done on <SPAN
>>>         class="xforms-submission" id="send"/>
>>>         1 -> TypeError: null is not an object (evaluating 'w.document')
>>>         0 -> Dispatching event xforms-submit-error on <SPAN
>>>         class="xforms-submission" id="send"/>
>>>
>>>
>>>         When I remove the show='new' it runs as expected.
>>>         Simple form demonstrating:
>>>
>>>         <?xml version="1.0" encoding="UTF-8"?>
>>>
>>>         <htmlxmlns="http://www.w3.org/1999/xhtml
>>>         <http://www.w3.org/1999/xhtml>"xmlns:xf="http://www.w3.org/2002/xforms
>>>         <http://www.w3.org/2002/xforms>"xmlns:xi="http://www.w3.org/2001/XInclude
>>>         <http://www.w3.org/2001/XInclude>"xmlns:ev="http://www.w3.org/2001/xml-events
>>>         <http://www.w3.org/2001/xml-events>"xmlns:tei="http://www.tei-c.org/ns/1.0
>>>         <http://www.tei-c.org/ns/1.0>">
>>>         <head>
>>>         <title>Syriaca.org: Create New Record</title>
>>>         <xf:model>
>>>         <xf:instancexmlns="http://www.tei-c.org/ns/1.0
>>>         <http://www.tei-c.org/ns/1.0>"id="i-uri-range">
>>>         <div>
>>>         <rangetype="test"start="2"end="3"who="4"note="5"/>
>>>         </div>
>>>         </xf:instance>
>>>         <xf:submissionid="send"method="post"show="new"replace="all"action="services/submit.xql"/>
>>>         </xf:model>
>>>         </head>
>>>         <bodystyle="margin:30px;">
>>>         <divclass="section">
>>>         <h1>Test submit</h1>
>>>         <xf:submitsubmission="send">
>>>         <xf:label>Submit</xf:label>
>>>         </xf:submit>
>>>         </div>
>>>         </body>
>>>         </html>
>>>
>>>         I'm running XSLTForms in eXist.
>>>
>>>         Is this a bug, or an incorrect use of the show attribute on
>>>         my part? I am trying to create a way for users to view and
>>>         download an instance without saving it.
>>>
>>>         Thanks for the help,
>>>
>>>         -Winona
>>>
>>>
>>>
>>>
>>>         ------------------------------------------------------------------------------
>>>         Check out the vibrant tech community on one of the world's most
>>>         engaging tech sites, Slashdot.org!http://sdm.link/slashdot
>>>
>>>         _______________________________________________
>>>         Xsltforms-support mailing list
>>>         Xsl...@li...
>>>         <mailto:Xsl...@li...>
>>>         https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>         <https://lists.sourceforge.net/lists/listinfo/xsltforms-support>
>>

Re: [Xsltforms-support] Question about show='new' in submission

[Winona S. <wsa...@gm...>]

Do you have any tips for downloading an instance without saving it?

Also, I noticed in Firefox, Chrome and Safari when clicking on any
xf:trigger I get bounced to the top of the page, this causes some grumbling
among my users since they then have to scroll down to the newly inserted
element. I would think the expected behavior would be to set the focus on
the new element? Any chance this could be an enhancement?

Thanks,
-Winona


On Tue, Apr 25, 2017 at 3:40 PM, Alain Couthures <
ala...@ag...> wrote:

> Hi Winona,
>
> The Profiler is, itself, an XForms page. It uses an XPath expression such
> as "serialize(instance('view'),'application/xml','yes')" where the third
> parameter is about indentation.
>
> --Alain
>
> Le 22/04/17 à 14:24, Winona Salesky a écrit :
>
> Yes disable the popup blocker did fix this. I think adding a try catch
> could be useful.
> Is there different way to allow users to view the XML instance data? For
> example, perhaps I could take advantage of some of the code that the
> profiler uses, but just isolate the instance information?
> Thanks for your help!
> -Winona
>
>
> On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures <
> ala...@ag...> wrote:
>
>> Hi Winona,
>>
>> I suspect that this issue is just due to pop-ups not being allowed.
>>
>> The error about w.document is just after this instruction: var w =
>> window.open("about:blank","_blank");
>>
>> I should probably wrap this with a try-catch statement just to alert
>> users about allowing popup. What do you think?
>>
>> --Alain
>>
>> Le 21/04/17 à 23:15, Winona Salesky a écrit :
>>
>> Hi All,
>> I'm trying to open my instance in a new window, using a submission with
>> show='new' and am getting this error:
>>
>> 0 -> Dispatching event xforms-submit on <SPAN class="xforms-submission"
>> id="send"/>
>> 0 -> Dispatching event xforms-submit-serialize on <SPAN
>> class="xforms-submission" id="send"/>
>> 1 -> Submit post - application/xml - services/submit.xql - false
>> 5 -> Dispatching event xforms-submit-done on <SPAN
>> class="xforms-submission" id="send"/>
>> 1 -> TypeError: null is not an object (evaluating 'w.document')
>> 0 -> Dispatching event xforms-submit-error on <SPAN
>> class="xforms-submission" id="send"/>
>>
>>
>> When I remove the show='new' it runs as expected.
>> Simple form demonstrating:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/20
>> 02/xforms" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:ev="
>> http://www.w3.org/2001/xml-events" xmlns:tei="http://www.tei-c.org/ns/1.0
>> ">
>>     <head>
>>         <title>Syriaca.org: Create New Record</title>
>>         <xf:model>
>>             <xf:instance xmlns="http://www.tei-c.org/ns/1.0" id=
>> "i-uri-range">
>>                 <div>
>>                     <range type="test" start="2" end="3" who="4" note="5"
>> />
>>                 </div>
>>             </xf:instance>
>>             <xf:submission id="send" method="post" show="new" replace=
>> "all" action="services/submit.xql"/>
>>         </xf:model>
>>     </head>
>>     <body style="margin:30px;">
>>         <div class="section">
>>             <h1>Test submit</h1>
>>             <xf:submit submission="send">
>>                 <xf:label>Submit</xf:label>
>>             </xf:submit>
>>         </div>
>>     </body>
>> </html>
>>
>> I'm running XSLTForms in eXist.
>>
>> Is this a bug, or an incorrect use of the show attribute on my part? I am
>> trying to create a way for users to view and download an instance without
>> saving it.
>>
>> Thanks for the help,
>>
>> -Winona
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>> _______________________________________________
>> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>

Re: [Xsltforms-support] Question about show='new' in submission

[Alain C. <ala...@ag...>]

Hi Winona,

The Profiler is, itself, an XForms page. It uses an XPath expression 
such as "serialize(instance('view'),'application/xml','yes')" where the 
third parameter is about indentation.

--Alain

Le 22/04/17 à 14:24, Winona Salesky a écrit :
> Yes disable the popup blocker did fix this. I think adding a try catch 
> could be useful.
> Is there different way to allow users to view the XML instance data? 
> For example, perhaps I could take advantage of some of the code that 
> the profiler uses, but just isolate the instance information?
> Thanks for your help!
> -Winona
>
>
> On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures 
> <ala...@ag... <mailto:ala...@ag...>> 
> wrote:
>
>     Hi Winona,
>
>     I suspect that this issue is just due to pop-ups not being allowed.
>
>     The error about w.document is just after this instruction: var w =
>     window.open("about:blank","_blank");
>
>     I should probably wrap this with a try-catch statement just to
>     alert users about allowing popup. What do you think?
>
>     --Alain
>
>     Le 21/04/17 à 23:15, Winona Salesky a écrit :
>>     Hi All,
>>     I'm trying to open my instance in a new window, using a
>>     submission with show='new' and am getting this error:
>>
>>     0 -> Dispatching event xforms-submit on <SPAN
>>     class="xforms-submission" id="send"/>
>>     0 -> Dispatching event xforms-submit-serialize on <SPAN
>>     class="xforms-submission" id="send"/>
>>     1 -> Submit post - application/xml - services/submit.xql - false
>>     5 -> Dispatching event xforms-submit-done on <SPAN
>>     class="xforms-submission" id="send"/>
>>     1 -> TypeError: null is not an object (evaluating 'w.document')
>>     0 -> Dispatching event xforms-submit-error on <SPAN
>>     class="xforms-submission" id="send"/>
>>
>>
>>     When I remove the show='new' it runs as expected.
>>     Simple form demonstrating:
>>
>>     <?xml version="1.0" encoding="UTF-8"?>
>>
>>     <htmlxmlns="http://www.w3.org/1999/xhtml
>>     <http://www.w3.org/1999/xhtml>"xmlns:xf="http://www.w3.org/2002/xforms
>>     <http://www.w3.org/2002/xforms>"xmlns:xi="http://www.w3.org/2001/XInclude
>>     <http://www.w3.org/2001/XInclude>"xmlns:ev="http://www.w3.org/2001/xml-events
>>     <http://www.w3.org/2001/xml-events>"xmlns:tei="http://www.tei-c.org/ns/1.0
>>     <http://www.tei-c.org/ns/1.0>">
>>     <head>
>>     <title>Syriaca.org: Create New Record</title>
>>     <xf:model>
>>     <xf:instancexmlns="http://www.tei-c.org/ns/1.0
>>     <http://www.tei-c.org/ns/1.0>"id="i-uri-range">
>>     <div>
>>     <rangetype="test"start="2"end="3"who="4"note="5"/>
>>     </div>
>>     </xf:instance>
>>     <xf:submissionid="send"method="post"show="new"replace="all"action="services/submit.xql"/>
>>     </xf:model>
>>     </head>
>>     <bodystyle="margin:30px;">
>>     <divclass="section">
>>     <h1>Test submit</h1>
>>     <xf:submitsubmission="send">
>>     <xf:label>Submit</xf:label>
>>     </xf:submit>
>>     </div>
>>     </body>
>>     </html>
>>
>>     I'm running XSLTForms in eXist.
>>
>>     Is this a bug, or an incorrect use of the show attribute on my
>>     part? I am trying to create a way for users to view and download
>>     an instance without saving it.
>>
>>     Thanks for the help,
>>
>>     -Winona
>>
>>
>>
>>
>>     ------------------------------------------------------------------------------
>>     Check out the vibrant tech community on one of the world's most
>>     engaging tech sites, Slashdot.org!http://sdm.link/slashdot
>>
>>     _______________________________________________
>>     Xsltforms-support mailing list
>>     Xsl...@li...
>>     <mailto:Xsl...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>     <https://lists.sourceforge.net/lists/listinfo/xsltforms-support>
>

Re: [Xsltforms-support] Question about show='new' in submission

[Winona S. <wsa...@gm...>]

Yes, also think this would be a useful addition to XForms. It is a bit
awkward to enable a download without saving the instance first. I can
imagine many use cases for this sort of functionality.

-Winona


On Sat, Apr 22, 2017 at 12:02 PM, Steven Pemberton <ste...@cw...>
wrote:

> I've often thought it would be useful to have a null action in XForms,
> that does no more than serialize, and rather than sending it anywhere, just
> re-reads it as if it has been sent to a server that just echos it back.
>
> Steven
>
>
> On Sat, 22 Apr 2017 14:24:25 +0200, Winona Salesky <wsa...@gm...>
> wrote:
>
> Yes disable the popup blocker did fix this. I think adding a try catch
> could be useful.
> Is there different way to allow users to view the XML instance data? For
> example, perhaps I could take advantage of some of the code that the
> profiler uses, but just isolate the instance information?
> Thanks for your help!
> -Winona
>
>
> On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures <
> ala...@ag...> wrote:
>
>> Hi Winona,
>>
>> I suspect that this issue is just due to pop-ups not being allowed.
>>
>> The error about w.document is just after this instruction: var w =
>> window.open("about:blank","_blank");
>>
>> I should probably wrap this with a try-catch statement just to alert
>> users about allowing popup. What do you think?
>>
>> --Alain
>>
>> Le 21/04/17 à 23:15, Winona Salesky a écrit :
>>
>> Hi All,
>> I'm trying to open my instance in a new window, using a submission with
>> show='new' and am getting this error:
>>
>> 0 -> Dispatching event xforms-submit on <SPAN class="xforms-submission"
>> id="send"/>
>> 0 -> Dispatching event xforms-submit-serialize on <SPAN
>> class="xforms-submission" id="send"/>
>> 1 -> Submit post - application/xml - services/submit.xql - false
>> 5 -> Dispatching event xforms-submit-done on <SPAN
>> class="xforms-submission" id="send"/>
>> 1 -> TypeError: null is not an object (evaluating 'w.document')
>> 0 -> Dispatching event xforms-submit-error on <SPAN
>> class="xforms-submission" id="send"/>
>>
>>
>> When I remove the show='new' it runs as expected.
>> Simple form demonstrating:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>>
>> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/
>> 2002/xforms" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:ev="
>> http://www.w3.org/2001/xml-events" xmlns:tei="http://www.tei-c.org/ns/1.0
>> ">
>>     <head>
>>         <title>Syriaca.org: Create New Record</title>
>>         <xf:model>
>>             <xf:instance xmlns="http://www.tei-c.org/ns/1.0" id=
>> "i-uri-range">
>>                 <div>
>>                     <range type="test" start="2" end="3" who="4" note="5"
>> />
>>                 </div>
>>             </xf:instance>
>>             <xf:submission id="send" method="post" show="new" replace=
>> "all" action="services/submit.xql"/>
>>         </xf:model>
>>     </head>
>>     <body style="margin:30px;">
>>         <div class="section">
>>             <h1>Test submit</h1>
>>             <xf:submit submission="send">
>>                 <xf:label>Submit</xf:label>
>>             </xf:submit>
>>         </div>
>>     </body>
>> </html>
>>
>> I'm running XSLTForms in eXist.
>>
>> Is this a bug, or an incorrect use of the show attribute on my part? I am
>> trying to create a way for users to view and download an instance without
>> saving it.
>>
>> Thanks for the help,
>>
>> -Winona
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>>
>>
>
>
>
>

Re: [Xsltforms-support] Question about show='new' in submission

[Steven P. <ste...@cw...>]

I've often thought it would be useful to have a null action in XForms,  
that does no more than serialize, and rather than sending it anywhere,  
just re-reads it as if it has been sent to a server that just echos it  
back.

Steven


On Sat, 22 Apr 2017 14:24:25 +0200, Winona Salesky <wsa...@gm...>  
wrote:

> Yes disable the popup blocker did fix this. I think adding a try catch  
> could be useful.Is there different way to allow users to view the XML  
> instance data? For example, perhaps I could take advantage of some of  
> the code that the profiler uses, but just isolate >the instance  
> information?Thanks for your help!
> -Winona
>
>
> On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures  
> <ala...@ag...> wrote:
>> Hi Winona,
>>
>> I suspect that this issue is just due to pop-ups not being allowed.
>>
>> The error about w.document is just after this instruction: var w =  
>> window.open("about:blank","_blank");
>>
>> I should probably wrap this with a try-catch statement just to alert  
>> users about allowing popup. What do you think?
>>
>> --Alain
>>
>> Le 21/04/17 à 23:15, Winona Salesky a écrit :
>>> Hi All, I'm trying to open my instance in a new window, using a  
>>> submission with show='new' and am getting this error:
>>> 0 -> Dispatching event xforms-submit on <SPAN  
>>> class="xforms-submission" id="send"/>
>>> 0 -> Dispatching event xforms-submit-serialize on <SPAN  
>>> class="xforms-submission" id="send"/>
>>> 1 -> Submit post - application/xml - services/submit.xql - false
>>> 5 -> Dispatching event xforms-submit-done on <SPAN  
>>> class="xforms-submission" id="send"/>
>>> 1 -> TypeError: null is not an object (evaluating 'w.document')
>>> 0 -> Dispatching event xforms-submit-error on <SPAN  
>>> class="xforms-submission" id="send"/>
>>>
>>>>>>
>>>>>> When I remove the show='new' it runs as expected.
>>> Simple form demonstrating:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>>
>>> <html xmlns="http://www.w3.org/1999/xhtml"  
>>> xmlns:xf="http://www.w3.org/2002/xforms"  
>>> xmlns:xi="http://www.w3.org/2001/XInclude"  
>>> xmlns:ev="http://www.w3.org/2001/>>>xml-events"  
>>> xmlns:tei="http://www.tei-c.org/ns/1.0">
>>>    <head>
>>>        <title>Syriaca.org: Create New Record</title>
>>>        <xf:model>
>>>            <xf:instance xmlns="http://www.tei-c.org/ns/1.0"  
>>> id="i-uri-range">
>>>                <div>
>>>                    <range type="test" start="2" end="3" who="4"  
>>> note="5"/>
>>>                </div>
>>>            </xf:instance>
>>>            <xf:submission id="send" method="post" show="new"  
>>> replace="all" action="services/submit.xql"/>
>>>        </xf:model>
>>>    </head>
>>>    <body style="margin:30px;">
>>>        <div class="section">
>>>            <h1>Test submit</h1>
>>>            <xf:submit submission="send">
>>>                <xf:label>Submit</xf:label>
>>>            </xf:submit>
>>>        </div>
>>>    </body>
>>> </html>
>>>
>>> I'm running XSLTForms in eXist.
>>>
>>> Is this a bug, or an incorrect use of the show attribute on my part? I  
>>> am trying to create a way for users to view and download an instance  
>>> without saving it.  
>>> Thanks for the help,
>>>
>>> -Winona
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>>
>>> _______________________________________________
>>> Xsltforms-support mailing list
>>> Xsl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Re: [Xsltforms-support] Question about show='new' in submission

[Winona S. <wsa...@gm...>]

Yes disable the popup blocker did fix this. I think adding a try catch
could be useful.
Is there different way to allow users to view the XML instance data? For
example, perhaps I could take advantage of some of the code that the
profiler uses, but just isolate the instance information?
Thanks for your help!
-Winona


On Sat, Apr 22, 2017 at 3:51 AM, Alain Couthures <
ala...@ag...> wrote:

> Hi Winona,
>
> I suspect that this issue is just due to pop-ups not being allowed.
>
> The error about w.document is just after this instruction: var w =
> window.open("about:blank","_blank");
>
> I should probably wrap this with a try-catch statement just to alert users
> about allowing popup. What do you think?
>
> --Alain
>
> Le 21/04/17 à 23:15, Winona Salesky a écrit :
>
> Hi All,
> I'm trying to open my instance in a new window, using a submission with
> show='new' and am getting this error:
>
> 0 -> Dispatching event xforms-submit on <SPAN class="xforms-submission"
> id="send"/>
> 0 -> Dispatching event xforms-submit-serialize on <SPAN
> class="xforms-submission" id="send"/>
> 1 -> Submit post - application/xml - services/submit.xql - false
> 5 -> Dispatching event xforms-submit-done on <SPAN
> class="xforms-submission" id="send"/>
> 1 -> TypeError: null is not an object (evaluating 'w.document')
> 0 -> Dispatching event xforms-submit-error on <SPAN
> class="xforms-submission" id="send"/>
>
>
> When I remove the show='new' it runs as expected.
> Simple form demonstrating:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/
> 2002/xforms" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:ev="
> http://www.w3.org/2001/xml-events" xmlns:tei="http://www.tei-c.org/ns/1.0"
> >
>     <head>
>         <title>Syriaca.org: Create New Record</title>
>         <xf:model>
>             <xf:instance xmlns="http://www.tei-c.org/ns/1.0" id=
> "i-uri-range">
>                 <div>
>                     <range type="test" start="2" end="3" who="4" note="5"
> />
>                 </div>
>             </xf:instance>
>             <xf:submission id="send" method="post" show="new" replace=
> "all" action="services/submit.xql"/>
>         </xf:model>
>     </head>
>     <body style="margin:30px;">
>         <div class="section">
>             <h1>Test submit</h1>
>             <xf:submit submission="send">
>                 <xf:label>Submit</xf:label>
>             </xf:submit>
>         </div>
>     </body>
> </html>
>
> I'm running XSLTForms in eXist.
>
> Is this a bug, or an incorrect use of the show attribute on my part? I am
> trying to create a way for users to view and download an instance without
> saving it.
>
> Thanks for the help,
>
> -Winona
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] Question about show='new' in submission

[Alain C. <ala...@ag...>]

Hi Winona,

I suspect that this issue is just due to pop-ups not being allowed.

The error about w.document is just after this instruction: var w = 
window.open("about:blank","_blank");

I should probably wrap this with a try-catch statement just to alert 
users about allowing popup. What do you think?

--Alain

Le 21/04/17 à 23:15, Winona Salesky a écrit :
> Hi All,
> I'm trying to open my instance in a new window, using a submission 
> with show='new' and am getting this error:
>
> 0 -> Dispatching event xforms-submit on <SPAN 
> class="xforms-submission" id="send"/>
> 0 -> Dispatching event xforms-submit-serialize on <SPAN 
> class="xforms-submission" id="send"/>
> 1 -> Submit post - application/xml - services/submit.xql - false
> 5 -> Dispatching event xforms-submit-done on <SPAN 
> class="xforms-submission" id="send"/>
> 1 -> TypeError: null is not an object (evaluating 'w.document')
> 0 -> Dispatching event xforms-submit-error on <SPAN 
> class="xforms-submission" id="send"/>
>
>
> When I remove the show='new' it runs as expected.
> Simple form demonstrating:
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <htmlxmlns="http://www.w3.org/1999/xhtml"xmlns:xf="http://www.w3.org/2002/xforms"xmlns:xi="http://www.w3.org/2001/XInclude"xmlns:ev="http://www.w3.org/2001/xml-events"xmlns:tei="http://www.tei-c.org/ns/1.0">
> <head>
> <title>Syriaca.org: Create New Record</title>
> <xf:model>
> <xf:instancexmlns="http://www.tei-c.org/ns/1.0"id="i-uri-range">
> <div>
> <rangetype="test"start="2"end="3"who="4"note="5"/>
> </div>
> </xf:instance>
> <xf:submissionid="send"method="post"show="new"replace="all"action="services/submit.xql"/>
> </xf:model>
> </head>
> <bodystyle="margin:30px;">
> <divclass="section">
> <h1>Test submit</h1>
> <xf:submitsubmission="send">
> <xf:label>Submit</xf:label>
> </xf:submit>
> </div>
> </body>
> </html>
>
> I'm running XSLTForms in eXist.
>
> Is this a bug, or an incorrect use of the show attribute on my part? I 
> am trying to create a way for users to view and download an instance 
> without saving it.
>
> Thanks for the help,
>
> -Winona
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Question about show='new' in submission

[Winona S. <wsa...@gm...>]

Hi All,
I'm trying to open my instance in a new window, using a submission with
show='new' and am getting this error:

0 -> Dispatching event xforms-submit on <SPAN class="xforms-submission"
id="send"/>
0 -> Dispatching event xforms-submit-serialize on <SPAN
class="xforms-submission" id="send"/>
1 -> Submit post - application/xml - services/submit.xql - false
5 -> Dispatching event xforms-submit-done on <SPAN
class="xforms-submission" id="send"/>
1 -> TypeError: null is not an object (evaluating 'w.document')
0 -> Dispatching event xforms-submit-error on <SPAN
class="xforms-submission" id="send"/>


When I remove the show='new' it runs as expected.
Simple form demonstrating:

<?xml version="1.0" encoding="UTF-8"?>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="
http://www.w3.org/2002/xforms" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:tei="
http://www.tei-c.org/ns/1.0">
    <head>
        <title>Syriaca.org: Create New Record</title>
        <xf:model>
            <xf:instance xmlns="http://www.tei-c.org/ns/1.0" id=
"i-uri-range">
                <div>
                    <range type="test" start="2" end="3" who="4" note="5"/>
                </div>
            </xf:instance>
            <xf:submission id="send" method="post" show="new" replace="all"
action="services/submit.xql"/>
        </xf:model>
    </head>
    <body style="margin:30px;">
        <div class="section">
            <h1>Test submit</h1>
            <xf:submit submission="send">
                <xf:label>Submit</xf:label>
            </xf:submit>
        </div>
    </body>
</html>

I'm running XSLTForms in eXist.

Is this a bug, or an incorrect use of the show attribute on my part? I am
trying to create a way for users to view and download an instance without
saving it.

Thanks for the help,

-Winona

Re: [Xsltforms-support] [Exist-open] 3.1.1 XSLTForms Demo Contacts example fails

[Dominique R. <dr...@gm...>]

XSLTForms Demo eXist 3.1.1

/db/apps/XSLTForms-Demo/data collection
the file contact.xml is empty (I have opened it in eXide)

2017-03-28 20:36 GMT+02:00 Dominique Rabeuf <dr...@gm...>:

> I will inspect the execution of XSLTForms «Contacts» sample.
> It is the *only *hat doesnot work in 3.1.1 (as far as I know)
>
> TinyMCE also, but already fails within 2.x (probably TinyMCE integration
> problem in XSLTForms)
>
> 2017-03-28 20:17 GMT+02:00 Joe Wicentowski <jo...@gm...>:
>
>> Winona, XSLTForms *should* be installed when you install XSLTForms-Demo,
>> since the latter registers the former as a dependency at
>> https://github.com/eXist-db/xsltforms-demo-app/blob/master/
>> expath-pkg.xml.tmpl#L3.
>>
>> Dominique, exist-db.org is still running 2.2 and old versions of
>> most/all apps, so there could certainly be changes in 3.x that have
>> cropped up in the meantime.  Do you see any errors in exist.log or in
>> your browser's console (e.g., Chrome's Developer Tools > Console)
>> indicating javascript or other errors?
>>
>> On Tue, Mar 28, 2017 at 1:41 PM, Winona Salesky <wsa...@gm...>
>> wrote:
>> > I noticed that XSLTForms is not deployed with eXist in the latest
>> release,
>> > you will need to install it via the package manger.
>> >
>> > -Winona
>> >
>> >
>> > On Tue, Mar 28, 2017 at 1:12 PM, Dominique Rabeuf <dr...@gm...>
>> wrote:
>> >>
>> >>
>> >> Version 3.1.1
>> >>
>> >> http://localhost:8080/exist/apps/XSLTForms-Demo/modules/form
>> .xq?form=contact.xml
>> >> Blank Window as result
>> >>
>> >> While (exist site)
>> >>
>> >> http://exist-db.org/exist/apps/XSLTForms-Demo/modules/form.
>> xq?form=contact.xml
>> >> Works
>> >>
>> >> --
>> >> Dominique Rabeuf
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------
>> ------------------
>> >> Check out the vibrant tech community on one of the world's most
>> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> Exi...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >>
>> >
>> >
>> > ------------------------------------------------------------
>> ------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> > _______________________________________________
>> > Exist-open mailing list
>> > Exi...@li...
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>>
>
>
>
> --
> *Dominique Rabeuf*
>



-- 
*Dominique Rabeuf*

Re: [Xsltforms-support] Trouble with setvalue in Firefox

[Tim T. <tim...@gm...>]

Thank you, Alain! The issue seems to have been fixed by rewriting the
xf:select1 with xf:copy rather than xf:item/xf:value (which was technically
incorrect anyway because my values contained internal spaces). It does seem
a bit slower now, so I may end up offloading the instance data onto the
server side.

Best regards,

Tim

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library

www.linkedin.com/in/timathompson
ta...@pr...

On Fri, Mar 17, 2017 at 9:26 AM, Alain Couthures <
ala...@ag...> wrote:

> Hello Tim,
>
> I have tested with both Firefox 52.0 and Firefox 54.0a and I can easily
> reproduce this crash creating just 5 or 6 items.
>
> It might be due to memory management but, unfortunately, using the browser
> debugger does not help at all to locate this issue.
>
> I have discovered that it is possible to run Firefox in safe mode which
> means, at least, no activated plugin, no theme and no hardware acceleration.
>
> Surprisingly, I cannot reproduce this crash in safe mode! Actually, my 2
> browsers did not already have any plugins so I just tried back with or
> without hardware acceleration: crash again.
>
> Using another theme did not change anything (crash again) but, at least,
> the one I activated proposed to send a crash report to Mozilla Foundation
> while the default one never did...
>
> I am, of course, still perplex. You might try with a much lighter
> subjects2.xml file but, because it is well supported by IE11, this should
> not be the reason for the trouble.
>
> BTW, the value expression for the setvalue action is not correct in your
> test case: it should be "instance('subjects')/category/subject[@name =
> current()]/@uri".
>
> Thank you for your feedback!
>
> --Alain
>
>
> Le 3/15/2017 à 4:50 PM, Tim Thompson a écrit :
>
> Hello,
>
> I have a conditional select1 that pulls values from a vocabulary loaded
> into an instance. It works well in Chrome and (reasonably) well in IE,
> although much more slowly.
>
> However, when I insert new repeated elements and trigger a setvalue action
> on xforms-value-changed, I run into an issue with Firefox.
>
> It's somewhat tricky to reproduce, but if I add new elements and change
> the conditional value (in the second select1) several times in quick
> succession (usually three or four times), Firefox crashes without warning.
> This is Firefox 52.0 on Windows 7.
>
> Attached is a sample test case and associated data file.
>
> Thanks in advance,
>
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
> www.linkedin.com/in/timathompson
> ta...@pr...
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>

Re: [Xsltforms-support] Trouble with setvalue in Firefox

[Alain C. <ala...@ag...>]

Hello Tim,

I have tested with both Firefox 52.0 and Firefox 54.0a and I can easily 
reproduce this crash creating just 5 or 6 items.

It might be due to memory management but, unfortunately, using the 
browser debugger does not help at all to locate this issue.

I have discovered that it is possible to run Firefox in safe mode which 
means, at least, no activated plugin, no theme and no hardware acceleration.

Surprisingly, I cannot reproduce this crash in safe mode! Actually, my 2 
browsers did not already have any plugins so I just tried back with or 
without hardware acceleration: crash again.

Using another theme did not change anything (crash again) but, at least, 
the one I activated proposed to send a crash report to Mozilla 
Foundation while the default one never did...

I am, of course, still perplex. You might try with a much lighter 
subjects2.xml file but, because it is well supported by IE11, this 
should not be the reason for the trouble.

BTW, the value expression for the setvalue action is not correct in your 
test case: it should be "instance('subjects')/category/subject[@name = 
current()]/@uri".

Thank you for your feedback!

--Alain

Le 3/15/2017 à 4:50 PM, Tim Thompson a écrit :
> Hello,
>
> I have a conditional select1 that pulls values from a vocabulary 
> loaded into an instance. It works well in Chrome and (reasonably) well 
> in IE, although much more slowly.
>
> However, when I insert new repeated elements and trigger a setvalue 
> action on xforms-value-changed, I run into an issue with Firefox.
>
> It's somewhat tricky to reproduce, but if I add new elements and 
> change the conditional value (in the second select1) several times in 
> quick succession (usually three or four times), Firefox crashes 
> without warning. This is Firefox 52.0 on Windows 7.
>
> Attached is a sample test case and associated data file.
>
> Thanks in advance,
>
> Tim
>
> --
> Tim A. Thompson
> Metadata Librarian (Spanish/Portuguese Specialty)
> Princeton University Library
>
> www.linkedin.com/in/timathompson <http://www.linkedin.com/in/timathompson>
> ta...@pr... <mailto:ta...@pr...>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support