Could you please check with this minimal test case?
<html
xmlns="http://www.w3.org/1999/xhtml";
xmlns:xf="http://www.w3.org/2002/xforms";
>
<head>
<title>Select1 appearance="full"</title>
<xf:model>
<xf:instance id="volume">
<data xmlns="">
<is-orphan/>
</data>
</xf:instance>
</xf:model>
</head>
<body>
<xf:select1 ref="instance('volume')/is-orphan" appearance="full">
<xf:label>Orphan</xf:label>
<xf:item>
<xf:label>Yes</xf:label>
<xf:value>true</xf:value>
</xf:item>
<xf:item>
<xf:label>No</xf:label>
<xf:value>false</xf:value>
</xf:item>
</xf:select1>
</body>
</html>
Is the XSLT transformation performed at server-side?
-Alain
Le 15/03/2012 22:59, Joe Wicentowski a écrit :
Hi Alain,
Sorry, I just realized you said you could *not* reproduce the error.
I'll do some more testing. If I still have the error, is there a
more complete error message that I could send to help you?
Thanks again,
Joe
Sent from my iPhone
On Thursday, March 15, 2012 at 4:47 PM, Alain Couthures wrote:
Hi Joe,
I tested again with Chrome (17.0.963.79) and your code but didn't
succeed in reproducing this issue (Please have a look at the attached
browser capture on Windows).
The stack dump provided in your capture is pointing to a function used
to locate the Javascript object for the select1 control from an item.
Are you using Windows??
Thank you for your feedbacks!
-Alain
Le 15/03/2012 18:52, Joe Wicentowski a écrit :
Hi Alain and Conal,
Thanks for your replies. I've just now had the chance to check out
XSLTForms from SVN trunk (rev. 534) and try my code again in Chrome.
Alain - unfortunately, I am still seeing the same error, even using
rev. 534. I've attached an updated image showing the error I see in
Chrome (17.0.963.46 m). The code that is responsible for the error in
Chrome is:
<xf:select1 ref="instance('volume')/is-orphan" appearance="full">
<xf:label>Orphan</xf:label>
<xf:item>
<xf:label>Yes</xf:label>
<xf:value>true</xf:value>
</xf:item>
<xf:item>
<xf:label>No</xf:label>
<xf:value>false</xf:value>
</xf:item>
</xf:select1>
The same code works fine in Firefox (4.0). Removing
@appearance="full" eliminates the error in Chrome, but I would prefer
to see the radio buttons.
Thanks in advance for any suggestions!
Joe
p.s. Conal - you were correct in thinking that my @full="appearance"
was just a typo in my email, not in my code - but apologies for the
error.
On Thu, Feb 16, 2012 at 7:37 PM, Conal
Tuohy<conal.tu...@versi.edu.au> wrote:
Maybe this is just a typo in your email, Joe, but shouldn't you have
@appearance="full"?
On 16/02/12 08:40, Joe Wicentowski wrote:
Hello,
I have a form that fails in Chrome (17.0) when I add the
@full="appearance" attribute on a select1 element. Without the
attribute, the form displays without error, but with the attribute, I
get an error - please see my attached image.
When I use Firefox (4.0), the form works whether I have this
attribute or
not.
Could you please let me know if this is a known issue with XSLTForms
Beta 3, or suggest some troubleshooting steps? I'm happy to test.
Thanks,
Joe
--
Conal Tuohy
eResearch Business Analyst
Victorian eResearch Strategic Initiative
+61-466324297
Attachments:
- select1-chrome.png
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Xsltforms-support mailing list
Xsltforms-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
