xsltforms-support Mailing List for XSLTForms (Page 90)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi Stephen,
> Apparently jquery is 
> not namespace aware.
>   
Did you try with method="html" instead of method="xml"

Thank you for your feedbacks!

-Alain



Hi Folks

I spent most of today looking at how to use the AnyTime calendar widget 
with XSLTForms. Its not easy to integrate the two due to to AnyTimes' 
dependancy on jQuery.

Seems that jQuery does not work in FF 3.5+ when using XSLT to generate 
the page (see: http://dev.jquery.com/ticket/4895). Apparently jquery is 
not namespace aware.

This might stop others going down the same blind alley.






-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html




After searching through the specs, i realized that my patch in
function Binding.evaluate()
would case the engine to scream
even for non-existent bidnings on actions, which it is not correct(!),
according to Xforms.1.1-chapter 4.7, see:
* http://www.w3.org/TR/xforms11/#idref-resolve
* http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt04/4.7/4.7.a.xhtml

Nevertheless, the problem is very annoying when building xforms
because is difficult to debug typos,
particularly when merging from different forms.

The proper behavior would be to issue 'xforms-binding-exceptions', asd
spec'ed by XForms1.1 chapter 4.5.1


Additionaly i found that there is another category of annoying
fail-to-report binding problems.
These are when a 'bind', 'ref', 'nodeset' and 'value' IDERF attributes
are themselfs the empty-string ('') or absent altogether.
These problems cannot be detected from within Binding.evaluate() since
there is no binding object to begin with!

The problem is demonstrated with the 'emptyBindings.xml' xforms below.



Ideally, i would like to have a solution that gathers all these errors
and reports them at once on model-construction with a single
xforms-binding-exception,
or afterwards, with some alert with a descriptive messages
facilitating pin-pointing the error
(since i have managed to build a formthat these errors were not
detected from the start)

Yet this check cannnot happen inside Binding.evaluate() but must be
separate for
* XFControl,
* XFCoreElement, and
* XFElement.



In a summury, i'm thinking that it may be necessary to add 3
functions, one per each super-class,
namely "evaluateBindings()" with different arguments each (3, 1, 1 respectively)
and they would perform the various sanity checks before invoking
this.binding.evaluate().
Their behavior on these 2 error categories would be different
depending on whether the model has been constructed or not.

Am i thinking along the correct lines, Alain?

Regards,
  Kostis



file: emptyBindings.xml
-------------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
"
>
  <head>
    <title>Control with Empty bind-id</title>
    <xf:model>
      <xf:instance>
       <root />
      </xf:instance>

      <xf:bind id="bind-with-no-nodeset"/>
    </xf:model>
  </head>

  <body>
    <xf:output id="should-not-fail-1" bind="bind-with-no-nodeset" />
    <xf:repeat id="should-not-fail-3" bind="bind-with-no-nodeset" />
    <xf:select1 id="should-not-fail-2" ref="/." >
      <xf:itemset bind="bind-with-no-nodeset" />
    </xf:select1>

    The control's empty-binding below fail with un-helpful err-messages.
    <xf:output />
    <xf:output ref="" />
    <xf:output value="" />

    <xf:select1  >
      <xf:itemset />
    </xf:select1>
    <xf:select1  >
      <xf:itemset nodeset="" />
    </xf:select1>

    <xf:select  >
      <xf:itemset />
    </xf:select>
    <xf:select  >
      <xf:itemset nodeset="" />
    </xf:select>

    <xf:repeat />
    <xf:repeat nodeset="" />

    <xf:group />
    <xf:group ref="" />

    <xf:label />
    <xf:label ref="" />

  </body>
</html>



On Thu, Apr 8, 2010 at 1:05 AM, Kostis Anagnostopoulos
<ank...@gm...> wrote:
> When a control's 'bind' attrribute refers to an xf:bind that does not exist,
> the javascript just fails with Null-Pointer message on browser console
> instead of reporting the bad bind-id.
>
> Reported against rev383, all browsers.
>
> The simple xform below reproduces the problem, and
> the following patch just issues a useful alert-window for each
> non-existent bind-id:
>
> Regards,
>  Kostis
>
> file: nonExistentBindId.xml:
> ------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
> type="text/xsl"?>
> <html
>  xmlns="http://www.w3.org/1999/xhtml"
>  xmlns:xf="http://www.w3.org/2002/xforms"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xsi:schemaLocation="
>     http://www.w3.org/2002/xforms
> http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
> "
>>
>  <head>
>    <title>Control with non-existent bind-id</title>
>
>  </head>
>
>  <body>
>    The output control's binding below silently fails
>    (with an un-helpful null-pointer err-message visible only on the
> browser's console).
>    <xf:output bind="missing-bind-id" />
>    <xf:output bind="missing-bind-id2" />
>  </body>
> </html>
>
>
> file: nonExistentBindId.diff
> ----------------
> Index: src/js/main/Binding.js.xml
> ===================================================================
> --- src/js/main/Binding.js.xml  (revision 383)
> +++ src/js/main/Binding.js.xml  (working copy)
> @@ -48,7 +48,14 @@
>        var result = null;
>        if (this.bind) {
>                if (typeof this.bind == "string") {
> -                       this.bind = $(this.bind).xfElement;
> +                       var idel = $(this.bind);
> +                       if (!idel) {
> +                               alert("Non-Existent bind-id: "+this.bind);
> +
> +                               // Do not fail here, to search for more missing ids.
> +                               return '';
> +                       }
> +                       this.bind = idel.xfElement;
>                }
>                result = this.bind.nodes;
>                copyArray(this.bind.depsNodes, depsNodes);
>

My simple workaround for this problem.

XFInstance.prototype.construct = function() {
    if (!xforms.ready) {
        if (this.src) {
            //SC
            this.src = 
this.src.replace(/&amp;/gi,"&").replace(/&lt;/gi,"<").replace(/&gt;/gi,">").replace(/&apos;/gi,"'");
            //end SC
            var cross = false;
            if (this.src.match(/^[a-zA-Z0-9+.-]+:\/\//)) {
                var domain = /^([a-zA-Z0-9+.-]+:\/\/[^\/]*)/;
                var sdom = domain.exec(this.src);
                var ldom = domain.exec(document.location.href);
                cross = sdom[0] != ldom[0];
            }

-------- Original Message --------
Subject: 	problem with & in src attribute of xform:instance in IE
Date: 	Wed, 07 Apr 2010 17:03:27 +1000
From: 	Stephen Cameron <ste...@ut...>
To: 	xsl...@li...



In recent XSLTForms revisions this error is occurring in IE 8.0 only.

an example from one of my xforms is:

           <xf:instance id="inst_project_person"
             
src="../../deegree-wfs/services?service=WFS&amp;version=1.1.0&amp;request=GetFeature&amp;namespace=xmlns(aatams=http://www.imos.org.au/aatams)&amp;typename=aatams:project_person" 
/"/>

On the server side this uri still contains &amp; rather than just & as 
the KVP separator character.

I can do more investigation, but I am wondering if this might be a 
regression?

Thanks



-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html




-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html




When a control's 'bind' attrribute refers to an xf:bind that does not exist,
the javascript just fails with Null-Pointer message on browser console
instead of reporting the bad bind-id.

Reported against rev383, all browsers.

The simple xform below reproduces the problem, and
the following patch just issues a useful alert-window for each
non-existent bind-id:

Regards,
  Kostis

file: nonExistentBindId.xml:
------------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
"
>
  <head>
    <title>Control with non-existent bind-id</title>

  </head>

  <body>
    The output control's binding below silently fails
    (with an un-helpful null-pointer err-message visible only on the
browser's console).
    <xf:output bind="missing-bind-id" />
    <xf:output bind="missing-bind-id2" />
  </body>
</html>


file: nonExistentBindId.diff
----------------
Index: src/js/main/Binding.js.xml
===================================================================

--- src/js/main/Binding.js.xml	(revision 383)
+++ src/js/main/Binding.js.xml	(working copy)
@@ -48,7 +48,14 @@
 	var result = null;
 	if (this.bind) {
 		if (typeof this.bind == "string") {
-			this.bind = $(this.bind).xfElement;
+			var idel = $(this.bind);
+			if (!idel) {
+				alert("Non-Existent bind-id: "+this.bind);
+				
+				// Do not fail here, to search for more missing ids.
+				return '';
+			}
+			this.bind = idel.xfElement;
 		}
 		result = this.bind.nodes;
 		copyArray(this.bind.depsNodes, depsNodes);

2 problems:

1) A xform with comments containing non-ASCII UTF-8 characters (greek
for instance)
prevents the xform from compiling in IE6 (currently cannot try ie 7 & 8).



2) In another similar issue in IE (6 & 7, 8 not tested),
i found problems when XPath handles text containing non-ASCII chars,
resulting into html-escaped-entities presented into the user.

I can work-arround these issues by avoiding placing I18N text directly
into XPath expressions,
and entering them into instance-doc nodes instead.




Both problems reported against rev383, IE6 (not tested with IE 7 & 8)
I apologize for not attempting to investigate when this issue was
firstly introduced.



The next 2 xforms, demonstrate both problems.
(Note that they contain greek characters, so they must be copied
verbatim from the mail text or use the attached ones)



file: commentsWithI18N.xml
--------------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html lang="el" xml:lang="el"
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
     http://www.w3.org/2001/xml-events
http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
"
>
  <head>
    <title>Comments with I18N</title>

    <xf:model id="model-main" >
      <xf:instance id="inst-doc" >
        <doc>
          <text> Some Text </text>
        </doc>
      </xf:instance>

    </xf:model>

  </head>

  <body>

    <!-- WARN: Due to the next comment, form fails on IE6.  Not tested
on ie 7 & 8. -->
    <!-- Καλημέρα! -->
    <xf:output value="text" />
  </body>
</html>



file: xpathWithI18N.xml
-----------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html lang="el" xml:lang="el"
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:ev="http://www.w3.org/2001/xml-events"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
     http://www.w3.org/2001/xml-events
http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
"
>
  <head>
    <title>XPath with I18N</title>
    <xf:model>
      <xf:instance>
        <root>
          <text>is non-translatable!</text>
        </root>
      </xf:instance>
    </xf:model>
  </head>

  <body>

    <xf:output value="concat('Φιλότιμο ', /root/text)" >
      <xf:label>The next I18N text fails(showing html-entities) on
IE6: </xf:label>
    </xf:output>
    <xf:trigger>
      <xf:label>xf:setvalue with I18n msg fails also in IE6!</xf:label>
      <xf:setvalue ev:event="DOMActivate"
      ref="/root/text">δεν μεταφράζεται!</xf:setvalue>
    </xf:trigger>
  </body>
</html>


Regards,
  Kostis

Reported against rev383.

In IE6, probably in "quirks-mode", the Core.getWindowSize() does not work
because there browser-capabilities decision path is not complete.

(as a result, on IE6 dialogs are badly centered, sometimes completely
outside of window visible area)


By applying the algorithm described here:
  http://www.howtocreate.co.uk/tutorials/javascript/browserwindow
i made a patch fixing the above problem:

I note that my patch is just a Quick 'n Dirty solution.
A more corrrect aproach would be to restructure the getWindowSize() code so as
to have a separate path only for the js-attributes that indeed differ
among browsers,
and a common path for the common ones.


Index: src/js/main/jsCore.js.xml
===================================================================
--- src/js/main/jsCore.js.xml	(revision 383)
+++ src/js/main/jsCore.js.xml	(working copy)
@@ -207,6 +207,16 @@
 					myOffsetY = Math.max(document.documentElement.clientHeight,
document.body.clientHeight); // body margins ?
 					myScrollX = document.body.parentNode.scrollLeft;
 					myScrollY = document.body.parentNode.scrollTop;
+                } else if( document.body && (
document.body.clientWidth || document.body.clientHeight ) ) {
+                    //IE 4 compatible
+                    myWidth = document.body.clientWidth;
+                    myHeight = document.body.clientHeight;
+                    myOffsetX =
Math.max(document.documentElement.clientWidth,
document.body.clientWidth); // body margins ?
+                    myOffsetY =
Math.max(document.documentElement.clientHeight,
document.body.clientHeight); // body margins ?
+                    myScrollX = document.body.parentNode.scrollLeft;
+                    myScrollY = document.body.parentNode.scrollTop;
+                } else {
+                    DebugConsole.write("Error: Cannot determine window-size!");
 				}
         return {
             height : myHeight,


---------------------
In order to test it, the xform i attached in the previous patch about
XFDialog demonstrates the problem since it usew the getWindowSize to
center the dialog.


I include it here just for reference:

-------------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html lang="el" xml:lang="el"
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:ev="http://www.w3.org/2001/xml-events"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
     http://www.w3.org/2001/xml-events
http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
"
>
  <head>
    <title>Dialog Test</title>

    <xf:model id="model-main" >
      <xf:instance id="inst-doc" >
        <doc>
          <text>
          Some Text
          </text>
        </doc>
      </xf:instance>

      <xf:bind id="bind-text" nodeset="text" />

    </xf:model>

  </head>

  <body>

    <xf:trigger>
      <xf:label>Show Dialog...</xf:label>
      <xf:show ev:event="DOMActivate" dialog="dlg-1" />
    </xf:trigger>

    <!-- A debug-aid dialog helping to collect the instance-documents
in XML.  -->
    <xf:dialog id="dlg-1" >
      <xf:label>
          Some Label:
      </xf:label>
      <xf:textarea bind="bind-text" style="width: 600px; height: 480px;"/>
      <xf:trigger>
        <xf:label>Ok</xf:label>
        <xf:hide ev:event="DOMActivate" dialog="dlg-1" />
      </xf:trigger>
    </xf:dialog>
  </body>
</html>

Reported against rev383, all browsers.

I suggest a minor css-improvement on the xf:dialog.

At the css declaration of 'div.xforms-dialog', there are the 'width'
and 'height' css atributes that define a *fixed* dialog-size.
Assuming that it is indeed necessary to define such a fixed size,
it would be more correct to use 'min-width' and 'min-height'
attributes instead,
both supported by all browsers, except IE6,
which let the developers to embed elements bigger than the default dialog-size.

But even on ie6, the ignored attributes mean that the dialog-size is
determined solely by its content,
which is quite satisfactory.

In general, it might be even prefferable to delete altogether the
'width' and 'height' css declarations for xf:dialog.

The next patch performs the initial suggestion:

Index: src/css/dialog.css.xml
===================================================================
--- src/css/dialog.css.xml  (revision 383)
+++ src/css/dialog.css.xml  (working copy)
@@ -27,8 +27,8 @@
 div.xforms-dialog {
    display             : none;
    position            : absolute;
-   width               : 400px;
-   height              : 300px;
+   min-width           : 400px;
+   min-height          : 300px;
    background-color    : white;
    border-top          : 1px solid black;
    border-left         : 1px solid black;


To test it, use the following xforms:

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" encoding="UTF-8"
type="text/xsl"?>
<html lang="el" xml:lang="el"
  xmlns="http://www.w3.org/1999/xhtml"
  xmlns:xf="http://www.w3.org/2002/xforms"
  xmlns:ev="http://www.w3.org/2001/xml-events"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="
     http://www.w3.org/2002/xforms
http://www.w3.org/MarkUp/Forms/2007/XForms-11-Schema.xsd
     http://www.w3.org/2001/xml-events
http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
"
>
  <head>
    <title>Dialog Test</title>

    <xf:model id="model-main" >
      <xf:instance id="inst-doc" >
        <doc>
          <text>
          Some Text
          </text>
        </doc>
      </xf:instance>

      <xf:bind id="bind-text" nodeset="text" />

    </xf:model>

  </head>

  <body>

    <xf:trigger>
      <xf:label>Show Dialog...</xf:label>
      <xf:show ev:event="DOMActivate" dialog="dlg-1" />
    </xf:trigger>

    <!-- A debug-aid dialog helping to collect the instance-documents
in XML.  -->
    <xf:dialog id="dlg-1" >
      <xf:label>
          Some Label:
      </xf:label>
      <xf:textarea bind="bind-text" style="width: 600px; height: 480px;"/>
      <xf:trigger>
        <xf:label>Ok</xf:label>
        <xf:hide ev:event="DOMActivate" dialog="dlg-1" />
      </xf:trigger>
    </xf:dialog>
  </body>
</html>

In recent XSLTForms revisions this error is occurring in IE 8.0 only.

an example from one of my xforms is:

            <xf:instance id="inst_project_person"
              
src="../../deegree-wfs/services?service=WFS&amp;version=1.1.0&amp;request=GetFeature&amp;namespace=xmlns(aatams=http://www.imos.org.au/aatams)&amp;typename=aatams:project_person" 
/"/>

On the server side this uri still contains &amp; rather than just & as 
the KVP separator character.

I can do more investigation, but I am wondering if this might be a 
regression?

Thanks



-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html




Hello Dan,
> Is there any way to also send login credentials (login/password) in 
> the HTTP header using this approach?
xf:header sub-element for xf:submission is not yet supported by 
XSLTForms but it shouldn't be very difficult to add this.

When would you like to experiment this ?

Thanks!

-Alain



Hello,

In the past (four years ago!) I used Subversion to store forms data by doing
HTTP PUTs directly into data collections.  This can be done by configuring
Apache to allow PUT and POST operations.

I documented this process here:
http://en.wikibooks.org/wiki/XForms/Versioning_Form_Data_With_WebDAV_and_Subversion

The trick was to configure Subversion as a WebDAV server and to turn *
SVNautoversioning* on so that each "Save" from a form would automatically do
a commit.

SVNAutoversioning on

Ih the past we did this in an Intranet so security was not a concern.

My question is has anyone figured out how to do this with XSLTForms on a
public server that is running SSL?  Our forms may be on different computers
then the SVN server.

Is there any way to also send login credentials (login/password) in the HTTP
header using this approach?

Thanks! - Dan
-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

I made a typo on the title of the new page i created:
http://en.wikibooks.org/wiki/XSLTForms/Extension_Funtions

Please fix it to 'Extension_FunCtions', since i don't have enough
permissions to move it myself,
and update also its link under
  'Status|XSLTForms only Extensions'


I apologize for this incovinience
  Kostis

On Mon, Apr 5, 2010 at 11:04 PM, COUTHURES Alain
<ala...@ag...> wrote:
> Kostis,
>>
>> I added a wiki page listing the available configuration options.
>>
>> http://en.wikibooks.org/wiki/XSLTForms/Configuration
>>
>> Please check if everything is correct or if something important is
>> missing.
>>
>
> I will as soon as possible.
>
> I'm glad to see wikibook enrichments!
>
> Thank you for sharing!
>
> -Alain
>



Kostis,
> I added a wiki page listing the available configuration options.
>
> http://en.wikibooks.org/wiki/XSLTForms/Configuration
>
> Please check if everything is correct or if something important is missing.
>   
I will as soon as possible.

I'm glad to see wikibook enrichments!

Thank you for sharing!

-Alain



David,
> Given a form that specifies an input type of integer, or any variant
> thereof, that also specifies incremental="true" doesn't work very well.
> When the initial negative sign is entered, it is replaced with the value
> "NaN" as can be seen in the sample form below.
>   
Yes, two bugs, indeed, in two regular expressions!
> The problem appears to be a result a conditional expression change in
> XFInput.setValue() made in rev 342.
This doesn't seem to be related to rev 342 so no problem about that...

Thank you for your feedbacks!

-Alain



David,
> I ran into some problems with openAction being called without an
> associated closeAction. The attached patch fixes the problems in
> XFSelect.js.xml and utils.js.xml.
In XFSelect.js.xml, the corresponding closeAction() call was effectively 
missing but I still don't see the necessity of moving openAction() call 
in utils.js.xml and it could induce at least extra refreshes. Do you 
have a simple test case about this ?

I have committed this anyway...
>  In addition, I rolled multiple
> instances of closeAction in XFSubmission.js.xml into a single call
> at the end of the submit function.
>   
This sounds more as a small source size reducing and this could change 
global behavior so I prefer not to commit this yet...

Thanks!

-Alain



David,
> There's a display problem with the popup calendar selection when the
> selected day is the first day of the month, causing the calendar cells
> corresponding to the previous month's days in the same week to have the
> "selected" class applied to them. The following patch (also attached in
> case the inline code is mangled) fixes the problem.
>
> - David
>   
Thanks you very much for this patch!

This is indeed an old problem I didn't consider as a priority but it's 
nice to see this fixed now.

-Alain



Hello Kostis,
> The 2 XSTLTForms extension function are not declared specificaly as
> xforms-funcs ,
> yet their definition expects them to be in this NS
> (http://www.w3.org/2002/xforms)
>   
You're right! I didn't detect this because prefixes are supported by 
XSLTForms for XPath functions. Have a look at 
http://www.agencexml.com/svg/svgbrowser.xml
> Was that indeed your intention, Alan?
> I mean, did you plan to add them on separate NS?
> (I remind that you have already apply this for is-valid() extra function,
> so it is also included in the xforms-NS.)
>
>   
I don't like the idea of requiring a specific namespace declaration. It 
isn't a compatibility issue anyway and users would forget it too often.

I don't like either to have to declare extension functions in XSLT 
sources but it's the only way to allow this...
> If yes,
> then the patch below fixes the bug so as these extra XSLTForms XPath
> functions to be available to the users of the library.
>   
Yes, even if it wasn't a bug ;-) ,  I have committed this!

Thanks!

-Alain



Hello Javier,
> we have corrected the error commenting line 233 of xsltforms.js:
>
> if (Core.isMozilla) { req.overrideMimeType("text/xml"); }
>
> But I don't know if this would affect to something else...
>   
According to MDC 
(https://developer.mozilla.org/en/AJAX/Getting_Started), "Some versions 
of some Mozilla browsers won't work properly if the response from the 
server doesn't have an XML |mime-type| header. To satisfy this, you can 
use an extra method call to override the header sent by the server, just 
in case it's not |text/xml|."

So I prefer not commenting this line now but this might happen if necessary.

Thanks!

-Alain

Hi Grégoire,
> Is there a way to access the instance data from my JavaScript function?
Of course!

Unfortunately, it isn't explicitly documented: you can look at wiki 
documentation and a browser debugger can also be very useful for that.

For instance data, from the span element, you have to access .xfElement.doc

Thanks!

-Alain



Hello Stephen,
> The alignment of the output is slightly different to the 
> inputs due to the presence of a small span (class="focus") on the left 
> of the input label but not with the output label. However if  in my css 
> i have
>
> span.focus {display:none;}
>
> the alignments do not change.
>
> Normally, I'd use a workaround for something like this but in this case 
> it may be of interest.
>
> Is it intended that the focus span will have some use?
>   
Actually, within AJAXForms, the focus span was activated and a red dot 
was always displayed. For compatibility reasons with other client-side 
implementations, I have just hidden it...

I still think that the focus span should be good for accessibility 
reasons and I prefer not to remove it. I consider your workaround as 
interesting! It will be committed soon.

Thanks!

-Alain



COUTHURES Alain escribió:
> Hello Javier,
>> I have an strange javascript error in firefox, when in a xml of 
>> xsltforms I am submitting using method=get and replace=all to a 
>> second xsltforms page. It seems to work ok, but the javascript error 
>> worries me.
>>
>> I have seen in 
>> http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt11/11.9/11.9.b.xhtml 
>> a test case that works exactly as my xmls, when pressing "Get Data" 
>> button, all seems to work ok, but in firefox error console I get:
>>
>> Error: mal formado
>> Archivo de origen: 
>> http://www.agencexml.com/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=White 
>>
>> Línea: 17, columna: 33
>> Código fuente:
>> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>>
>> It seems all problems are related with characters as &, <, >, that 
>> makes the resulting xml bad formed, because when I get the resulting 
>> xml from this request and validate with an xml parser I get:
>>
>>
>> $ xmllint --noout test.xml
>> test.xml:17: parser error : EntityRef: expecting ';'
>> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>>                                 ^
>> test.xml:17: parser error : EntityRef: expecting ';'
>> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>>                                             ^
>> test.xml:19: parser error : EntityRef: expecting ';'
>> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>>                                          ^
>> test.xml:19: parser error : EntityRef: expecting ';'
>> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>>                                                      ^
>> test.xml:29: parser error : EntityRef: expecting ';'
>> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi 
>>
>>                                                                 ^
>> test.xml:29: parser error : EntityRef: expecting ';'
>> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi 
>>
>>
>> The error is thrown in line 1910 os xsltforms.js, "req.send(null)", 
>> when getting the data to the browser with XMLHttpRequest.
>>   
> Sorry, I can't reproduce this in my test environment but I have 
> detected a problem with FireFox about replace="all" when in XHTML mode.
>
> This is not fixed yet... XHTML mode is better for SVG rendering but 
> HTML mode is required for some other Javascript framework integration. 
> To switch mode, just modify xslt output method: "html" for HTML or 
> "xml" for XHTML.
>
> Did you test in XHTML ou in HTML mode ?
I'm using r362, we will not update to last version for some weeks to 
avoid bugs of new features.

In my xsl we have "html":

<xsl:output method="html" encoding="iso-8859-1" 
omit-xml-declaration="no" indent="no" doctype-public="-//W3C//DTD XHTML 
1.0 Transitional//EN" 
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>
>
> Thanks!
>
> -Alain



Hello Javier,
> I have an strange javascript error in firefox, when in a xml of 
> xsltforms I am submitting using method=get and replace=all to a second 
> xsltforms page. It seems to work ok, but the javascript error worries me.
>
> I have seen in 
> http://www.agencexml.com/xforms-tests/testsuite/XForms1.1/Edition1/Chapt11/11.9/11.9.b.xhtml 
> a test case that works exactly as my xmls, when pressing "Get Data" 
> button, all seems to work ok, but in firefox error console I get:
>
> Error: mal formado
> Archivo de origen: 
> http://www.agencexml.com/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=White
> Línea: 17, columna: 33
> Código fuente:
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>
> It seems all problems are related with characters as &, <, >, that makes 
> the resulting xml bad formed, because when I get the resulting xml from 
> this request and validate with an xml parser I get:
>
>
> $ xmllint --noout test.xml
> test.xml:17: parser error : EntityRef: expecting ';'
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                 ^
> test.xml:17: parser error : EntityRef: expecting ';'
> QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                             ^
> test.xml:19: parser error : EntityRef: expecting ';'
> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                          ^
> test.xml:19: parser error : EntityRef: expecting ';'
> REDIRECT_QUERY_STRING=carOwner=Henry&make=Acura&color=White
>                                                      ^
> test.xml:29: parser error : EntityRef: expecting ';'
> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi
>                                                                 ^
> test.xml:29: parser error : EntityRef: expecting ';'
> REQUEST_URI=/xforms-tests/xsltforms/echo.php?carOwner=Henry&make=Acura&color=Whi
>
> The error is thrown in line 1910 os xsltforms.js, "req.send(null)", when 
> getting the data to the browser with XMLHttpRequest.
>   
Sorry, I can't reproduce this in my test environment but I have detected 
a problem with FireFox about replace="all" when in XHTML mode.

This is not fixed yet... XHTML mode is better for SVG rendering but HTML 
mode is required for some other Javascript framework integration. To 
switch mode, just modify xslt output method: "html" for HTML or "xml" 
for XHTML.

Did you test in XHTML ou in HTML mode ?

Thanks!

-Alain



I added a wiki page listing the available configuration options.

http://en.wikibooks.org/wiki/XSLTForms/Configuration

Please check if everything is correct or if something important is missing.

Regards
  Kostis



Given a form that specifies an input type of integer, or any variant
thereof, that also specifies incremental="true" doesn't work very well.
When the initial negative sign is entered, it is replaced with the value
"NaN" as can be seen in the sample form below.

The problem appears to be a result a conditional expression change in
XFInput.setValue() made in rev 342. What was the reasoning for the
change and what side effects would be expected if it's reverted? If the
change shouldn't be reverted, is there any other way to avoid the NaN
replacement when users (typically) enter a negative number starting with
the negative sign? I reverted the change locally and haven't seen any
problems with the forms I'm working with, but it's possible those forms
are not using any techniques that trigger the problem that resulted in
the change in rev 342.

- David


<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:xf="http://www.w3.org/2002/xforms"
      xmlns:ev="http://www.w3.org/2001/xml-events">
  <head>
    <title>Integer Validations</title>
    <xf:model>
      <xf:instance>
        <data xmlns=""> <I1/> <I2/> </data>
      </xf:instance>
      <xf:bind nodeset="/data/I1" id="i1" type="xf:negativeInteger" />
      <xf:bind nodeset="/data/I2" id="i2" type="xf:negativeInteger" />
      <xf:action ev:event="xforms-ready">
         <xf:setfocus control="input-1" />
      </xf:action>
    </xf:model>
  </head>
  <body>
    <p>
      This field does not use incremental validation.<br />
      <xf:input id="input-1" bind="i1">
        <xf:label>Enter a negative integer: </xf:label>
      </xf:input>
    </p>
    <p>
      This field uses incremental validation.<br />
      <xf:input id="input-2" bind="i2" incremental="true">
        <xf:label>Enter a negative integer: </xf:label>
      </xf:input>
    </p>
  </body>
</html>




I ran into some problems with openAction being called without an
associated closeAction. The attached patch fixes the problems in
XFSelect.js.xml and utils.js.xml. In addition, I rolled multiple
instances of closeAction in XFSubmission.js.xml into a single call
at the end of the submit function.

- David



2009	Jan	Feb	Mar	Apr (1)	May (6)	Jun (9)	Jul (16)	Aug (5)	Sep (43)	Oct (36)	Nov (58)	Dec (43)
2010	Jan (79)	Feb (81)	Mar (107)	Apr (93)	May (85)	Jun (54)	Jul (64)	Aug (54)	Sep (45)	Oct (53)	Nov (34)	Dec (77)
2011	Jan (56)	Feb (53)	Mar (52)	Apr (66)	May (44)	Jun (16)	Jul (28)	Aug (5)	Sep (15)	Oct (21)	Nov (51)	Dec (46)
2012	Jan (16)	Feb (38)	Mar (47)	Apr (45)	May (41)	Jun (41)	Jul (72)	Aug (17)	Sep (10)	Oct (16)	Nov (29)	Dec (30)
2013	Jan (25)	Feb (13)	Mar (20)	Apr (25)	May (34)	Jun (8)	Jul (12)	Aug (9)	Sep (21)	Oct (19)	Nov (6)	Dec (2)
2014	Jan (14)	Feb (8)	Mar (7)	Apr (13)	May (33)	Jun (13)	Jul (6)	Aug (5)	Sep (5)	Oct (34)	Nov (7)	Dec
2015	Jan (1)	Feb (6)	Mar (17)	Apr (12)	May (10)	Jun (18)	Jul (31)	Aug (9)	Sep (3)	Oct (6)	Nov (19)	Dec (1)
2016	Jan (18)	Feb (4)	Mar (13)	Apr (19)	May	Jun (17)	Jul (7)	Aug	Sep (3)	Oct (6)	Nov (3)	Dec
2017	Jan (5)	Feb (17)	Mar (4)	Apr (8)	May (3)	Jun	Jul (8)	Aug (2)	Sep	Oct (5)	Nov (6)	Dec (4)
2018	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (6)	Nov	Dec (1)
2019	Jan	Feb	Mar (4)	Apr (2)	May (4)	Jun	Jul	Aug (2)	Sep (7)	Oct	Nov	Dec
2020	Jan (13)	Feb (17)	Mar (8)	Apr (11)	May (15)	Jun (11)	Jul	Aug	Sep	Oct	Nov	Dec (6)
2021	Jan (9)	Feb (26)	Mar (17)	Apr	May (7)	Jun (18)	Jul	Aug	Sep	Oct	Nov	Dec (10)
2022	Jan	Feb (1)	Mar	Apr	May (3)	Jun	Jul	Aug (2)	Sep (3)	Oct (2)	Nov (10)	Dec (1)
2023	Jan (10)	Feb	Mar (7)	Apr (8)	May (3)	Jun	Jul	Aug	Sep (8)	Oct (11)	Nov (8)	Dec (5)
2024	Jan (7)	Feb (3)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2025	Jan (4)	Feb (2)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

xsltforms-support Mailing List for XSLTForms (Page 90)

xsltforms-support — XSLTForms support list