Thread: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

Brought to you by: alain-couthures

xsltforms-support

[Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Joe W. <jo...@gm...> - 2012-02-15 21:40:41

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

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Joe W. <jo...@gm...> - 2012-02-15 21:53:10

Attachments: xsltforms-error.jpg

Oops, here's the attachment showing the error.

Joe

On Wed, Feb 15, 2012 at 4:40 PM, Joe Wicentowski <jo...@gm...> 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

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Alain C. <ala...@ag...> - 2012-02-16 20:43:08

Hello Joe,

Yes, I think you should try with the latest SVN version of XSLTForms.

Recent versions of browsers have unexpectedly changed some of their 
behaviors.

Thank you for your feedbacks!

-Alain

Le 15/02/2012 22:52, Joe Wicentowski a écrit :
> Oops, here's the attachment showing the error.
>
> Joe
>
> On Wed, Feb 15, 2012 at 4:40 PM, Joe Wicentowski<jo...@gm...>  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
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization&  Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>>
>>
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Validation with Regular Expressions

From: William V. <wi...@bi...> - 2012-02-16 13:55:33

Hi list,

I'm couldn't find clear documentation about the right way of validating 
a field vs a regular expression (ie. email, credit-card, phone) client 
side (you can always validate on server vs schema, but this is not the 
case).

I've found in XForms documentation and other sources various methods to 
do this, but I'm not sure XSLTForms can support them:

- Specifying an Schema for the instance
- Using custom datatypes in the type attribute of xf:bind
- Using user defined functions in Javascript and calling it from bind 
constraints or xforms-value-changed event handler
- Maybe other...

Can somebody state the best method to do this with XSLTForms.

Thanks for all the help you can provide,


Bill

Re: [Xsltforms-support] Validation with Regular Expressions

From: Alain C. <ala...@ag...> - 2012-02-16 21:49:24

Hello Bill,

Yes, XSLTForms supports all of them.

Have a look at 5.2.6, 5.2.7.a and 5.2.7.b tests for xforms:email and 
xforms:card-number types.

Test 2.3.a is based on a regular expression.

It is possible with XSLTForms to define its own XPath functions with 
Javascript. Have a look at XsltForms_xpathCoreFunctions in xsltforms.js

Thank you for your feedbacks!

-Alain

Le 16/02/2012 14:55, William Velasquez a écrit :
> Hi list,
>
> I'm couldn't find clear documentation about the right way of validating
> a field vs a regular expression (ie. email, credit-card, phone) client
> side (you can always validate on server vs schema, but this is not the
> case).
>
> I've found in XForms documentation and other sources various methods to
> do this, but I'm not sure XSLTForms can support them:
>
> - Specifying an Schema for the instance
> - Using custom datatypes in the type attribute of xf:bind
> - Using user defined functions in Javascript and calling it from bind
> constraints or xforms-value-changed event handler
> - Maybe other...
>
> Can somebody state the best method to do this with XSLTForms.
>
> Thanks for all the help you can provide,
>
>
> Bill
>
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Conal T. <con...@ve...> - 2012-02-17 00:38:07

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

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Joe W. <jo...@gm...> - 2012-03-15 17:53:10

Attachments: xsltforms-error-appearance-full-in-chrome.jpg

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 <con...@ve...> 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
>

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Alain C. <ala...@ag...> - 2012-03-15 20:47:15

Attachments: select1-chrome.png

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<con...@ve...>  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
>>
>>

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Joe W. <jo...@gm...> - 2012-03-15 21:49:21

Hi Alain,  

Yes, I'm on Windows XP SP3 on this machine.

Thanks,
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<con...@ve...> 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
>

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Joe W. <jo...@gm...> - 2012-03-15 21:59:35

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<con...@ve...> 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
>

Re: [Xsltforms-support] Error with select1[@full = 'appearance'] in Chrome

From: Alain C. <ala...@ag...> - 2012-03-15 22:18:36

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<con...@ve...> 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
>