Recent changes to bugs

does not show for xforms-invalid event

Cristian Valentin Ganta — Thu, 02 Feb 2012 22:31:31 -0000

The alert icon does not show (display:none) for any expression of required or constraint attributes in the bind.
This used to work in pre-beta versions.

<xforms:bind id="fname_bind" nodeset="/person-name/first-name" required="true()" constraint="string-length(.) >0"/>

<xforms:input ref="/person-name/first-name">
<xforms:label>First Name:</xforms:label>
<xforms:alert>required!!!</xforms:alert>
</xforms:input>

switch/case/toggle fails in nested repeat

Leigh L. Klotz, Jr. — Fri, 08 Oct 2010 23:43:04 -0000

In repeat/repeat/switch/case/toggle, sometimes the wrong item gets toggled and then fails to toggle back.

See attached test case for xsltforms-dataisland-461.

Improper handling of quotes

Anonymous — Thu, 16 Sep 2010 06:06:25 -0000

The code

<xf:setvalue ref="instance('data')/error" value="substring-before(substring-after(event('response-body'),'s:Text xml:lang="ru-RU">'),'</s:Text')"/>

translates into

XPath.create("substring-before(substring-after(event('response-body'),'s:Text xml:lang="ru-RU">'),'</s:Text')",new FunctionCallExpr('http://www.w3.org/2005/xpath-functions substring-before',new FunctionCallExpr('http://www.w3.org/2005/xpath-functions substring-after',new FunctionCallExpr('http://www.w3.org/2002/xforms event',new CteExpr('response-body')),new CteExpr('s:Text xml:lang="ru-RU">')),new CteExpr('</s:Text')));

Note that "ru-RU" is not escaped. This causes
XSLTForms Exception -------------------------- Incorrect Javascript code generation

cannot delete attribute in dataisland

Leigh L. Klotz, Jr. — Tue, 14 Sep 2010 22:23:02 -0000

<delete nodeset="/path/to/@att" /> fails.

Same cause as other attribute bugs.

hexBinary and xsd:hexBinary and lowercase

Leigh L. Klotz, Jr. — Fri, 03 Sep 2010 18:02:46 -0000

XML Schema Part 2 allows lowercase for hexBinary, but specifies that uppercase be used in the canonical lexical representation.
http://www.w3.org/TR/xmlschema-2/#hexBinary-lexical-representation

I think two things should happen:
1. I think the patterns for both hexBinary should change to allow lowercase. That's because incoming XML with lowercase is correct.
2. I think the lexical conversion for controls bound to hexBinary should uppercase input when writing to the instance, to canonicalize it.

#1 is more important, and easier.
xsltforms.js:
"hexBinary" : {
"nsuri" : "http://www.w3.org/2002/xforms",
"patterns" : [ "^[0-9A-Fa-f]*$" ]
},

"hexBinary" : \{
    "nsuri" : "http://www.w3.org/2001/XMLSchema",
    "patterns" : \[ "^\[0-9A-Fa-f\]+$" \]
\}

Accept header not set

Leigh L. Klotz, Jr. — Tue, 17 Aug 2010 20:27:56 -0000

In submission replace='instance' the accept header is not set except in certain conditions:

            if \(method == "get" || method == "delete"\) \{
                if \(media == XFSubmission.SOAP\_\) \{
                    req.setRequestHeader\("Accept", mt\);
                \}

                req.send\(null\);
            \} else \{
                req.setRequestHeader\("Content-Type", mt\);

                if \(media == XFSubmission.SOAP\_\) \{
                    req.setRequestHeader\("SOAPAction", this.soapAction\);
                \}
                req.send\(Core.saveXML\(node\)\);
            \}

So it looks like the submission/mediatype is used to set the accept header in SOAP GET and DELETE requests, defaulting to application/xml, but it's not set at all in POST or PUT.

I propose that at least if subm.replace=="instance" that GET, PUT, and POST have Accept default to application/xml. It can be overridden using the XForms 1.1 headers element.

Date type

Dominique Rabeuf — Tue, 17 Aug 2010 15:27:35 -0000

XSLTForms Build 444

Entering incorrect dates do not fire type error.
For example a/b/c is accepted as a date (implicit conversion seems to be set to now() as seen in associated calendar table)

The dates whose year is less than 1000 are not supported.
For example 25/12/496 is converted to 25/01/1927.

The overflow values (days in the month and months number) are processed with some logic arithmetic, but this is not quite compliant.to ISO 8601
For example, 52/14/2010 becomes 24/03/2011

ancestor axis fails on attributes

Leigh L. Klotz, Jr. — Wed, 11 Aug 2010 23:22:57 -0000

Related to 3042659

cannot change attribute values

Leigh L. Klotz, Jr. — Tue, 10 Aug 2010 18:01:41 -0000

Possibly related to 3039052.

In dataisland branch r445, setvalue (and as a result for controls) cannot set attribute values.

setvalue, instance/@src, bind/@readonly

Leigh L. Klotz, Jr. — Tue, 03 Aug 2010 22:19:01 -0000

As reported in email

Also, it seems that binds at levels other than the root node fail as well, but not all of them.

The following combination fails in the dataisland branch, tested with r443 and r445:

<instance id="main" src="foo.xml" />
<instance id="controls"><data xmlns=""><locked>false</locked</data></instance>

<trigger>
<label>Edit</label>
<setvalue ev:event="DOMActivate" ref="instance('controls')/locked">false</setvalue>
</trigger>

The setvalue event happens, but the value of locked never changes, and the readonly MIP does not change.

The setvalue and MIP work OK when loading instance id="main" from inline content, but not from @src.
The setvalue works when the bind/@readonly is removed.
The setvalue and MIP work OK when the bind nodeset="instance('main')/BufferSize", but not when it's inherited from root.

Since XSLTForms has the non-standard restriction on one bind per node, it's important that the MIP inheritance and binding to instance root element work.

See the attached files showing the above examples complete.