xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Buttons triggered twice on FireFox.

[Benoit V. <bvi...@la...>]

Hi Alain,
      I use the latest release of Firefox on Windows.
      I tried to put alert(event.target.nodeName) just before the 
event.target.nodeName === "BUTTON" test and I get "BUTTON" with a 
smallxforms test and nanoxfserver, but I get "button" with my 
application forms. It's the same with Chrome.
     The main difference between nanoxfserver and my application is that 
the Xsltforms transformation is done server-side in my application. It's 
perhaps related to the problem.

Thank's
     Benoit

Le 05/05/2014 20:22, Alain Couthures a écrit :
> Hi Benoit,
>
> I have not reproduced this issue with latest version of Firefox for 
> Windows so I would be happy to know more precisely your user environment.
>
> According to HTML specifications, I think that names should always be 
> in upper case. Anyway, it is quite easy to add .toUpperCase() and it 
> will be committed in the next build!
>
> Thank you very much!
>
> -Alain
>
> Le 05/05/2014 15:45, Benoit VINCENT a écrit :
>> Hi Alain,
>> Since I have upgraded XSLTForms to r595, I encountered problems with my
>> triggers (normal appearance) used in Firefox (they work fine with
>> Chrome). There seems like the DOMactivate event was fired twice.
>> I searched in your commits and I found you have worked on events
>> bubbling in r585. In /src/js/xmlevtmngt/Listener.js.xml[87] you test :
>>
>>           event.target.nodeName === "BUTTON"
>>
>> I think that in Firefox the nodeName is in lower case. So I tried to 
>> add :
>>
>>           event.target.nodeName === "BUTTON" || event.target.nodeName 
>> ===
>> "button"
>>
>> and now, all works correctly with Firefox, miracle !
>>
>> Is it the good way to correct this bug ?
>>
>> Thank you for your help,
>>           Benoit
>>
>> ------------------------------------------------------------------------------ 
>>
>> Is your legacy SCM system holding you back? Join Perforce May 7 to 
>> find out:
>> • 3 signs your SCM is hindering your productivity
>> • Requirements for releasing software faster
>> • Expert tips and advice for migrating your SCM now
>> http://p.sf.net/sfu/perforce
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] Buttons triggered twice on FireFox.

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

Hi Benoit,

I have not reproduced this issue with latest version of Firefox for 
Windows so I would be happy to know more precisely your user environment.

According to HTML specifications, I think that names should always be in 
upper case. Anyway, it is quite easy to add .toUpperCase() and it will 
be committed in the next build!

Thank you very much!

-Alain

Le 05/05/2014 15:45, Benoit VINCENT a écrit :
> Hi Alain,
> Since I have upgraded XSLTForms to r595, I encountered problems with my
> triggers (normal appearance) used in Firefox (they work fine with
> Chrome). There seems like the DOMactivate event was fired twice.
> I searched in your commits and I found you have worked on events
> bubbling in r585. In /src/js/xmlevtmngt/Listener.js.xml[87] you test :
>
>           event.target.nodeName === "BUTTON"
>
> I think that in Firefox the nodeName is in lower case. So I tried to add :
>
>           event.target.nodeName === "BUTTON" || event.target.nodeName ===
> "button"
>
> and now, all works correctly with Firefox, miracle !
>
> Is it the good way to correct this bug ?
>
> Thank you for your help,
>           Benoit
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Buttons triggered twice on FireFox.

[Benoit V. <bvi...@la...>]

Hi Alain,
Since I have upgraded XSLTForms to r595, I encountered problems with my 
triggers (normal appearance) used in Firefox (they work fine with 
Chrome). There seems like the DOMactivate event was fired twice.
I searched in your commits and I found you have worked on events 
bubbling in r585. In /src/js/xmlevtmngt/Listener.js.xml[87] you test :

         event.target.nodeName === "BUTTON"

I think that in Firefox the nodeName is in lower case. So I tried to add :

         event.target.nodeName === "BUTTON" || event.target.nodeName === 
"button"

and now, all works correctly with Firefox, miracle !

Is it the good way to correct this bug ?

Thank you for your help,
         Benoit

[Xsltforms-support] digest() issues

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

Hi Alain,

Needed a base64 encoding function (to allow to download instance data document via a data URL link), and discovered that XSLTForms' implementation of the digest() xpath function can be used for this!

The function needs fixes on lines 6089 and 6090 in xsltforms.js: "l2" => "l2b".

Suggestion: The special BASE64 hashing algorithm could be specified as "xsltforms:BASE64" to be in compliance with the XForms spec.

Thanks for sharing your great XForms implementation!

Kind regards,
Mats

Re: [Xsltforms-support] Booting XsltForms from an instance data document

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

Hi Mats,

At line 9455, an exception occurs when an id for an XForms element is 
not found. This consistency issue might be due to an invalid id 
generation during the XSLT transformation.

-Alain

Le 04/05/2014 15:21, Mats Eklund a écrit :
> Hi Alain,
>
> I have managed to implement the javascript approach, and it works, so 
> I have a fallback solution.
>
> Meanwhile I was able to resolve the (first) problem with the ?xml-form 
> approach: I realized that the ?xml-form/@href of the form had to be 
> relative to the XSLTForms XSL document rather than the source XML 
> document. Now I however get a javascript exception at line 9455 in 
> xsltforms.js. Consistent behavior in all browsers. If I open the 
> referenced form directly (with same instance data), it loads without 
> problem.
>
> Any idea what this could be, or how to best troubleshoot?
>
> Kind regards,
> Mats
>

Re: [Xsltforms-support] Booting XsltForms from an instance data document

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

Hi Alain,

I have managed to implement the javascript approach, and it works, so I have a fallback solution.

Meanwhile I was able to resolve the (first) problem with the ?xml-form approach: I realized that the ?xml-form/@href of the form had to be relative to the XSLTForms XSL document rather than the source XML document. Now I however get a javascript exception at line 9455 in xsltforms.js. Consistent behavior in all browsers. If I open the referenced form directly (with same instance data), it loads without problem.

Any idea what this could be, or how to best troubleshoot?

Kind regards,
Mats




________________________________
 From: Alain Couthures <ala...@ag...>
To: Mats Eklund <mat...@ya...>; "xsl...@li..." <xsl...@li...> 
Sent: Sunday, May 4, 2014 1:21 PM
Subject: Re: [Xsltforms-support] Booting XsltForms from an instance data document
 


Hi Mats,

Because the document() function is not allowed by Chrome, I had to
      force the Profiler into the stylesheet itself...

Could please you try with another browser?

Is it an important feature for you? This could be rewritten with
      Javascript (and native XSLT engine launched with Javascript). What
      do you think?

Thanks!

-Alain


Le 04/05/2014 11:52, Mats Eklund a écrit :

Hi Alain,
>
>I tried the ?xml-form approach, however, the resulting page is
        an XSLTForms Profiler page rather than the form!? Am I doing
        something wrong then? 
>
>My xml file looks like this:
>
><?xml version="1.0" encoding="UTF-8"?>
><?xml-stylesheet href="xsltforms/xsltforms.xsl"
        type="text/xsl"?>
><?xml-form type="application/xhtml+xml" href="myform.xhtml"
        instance="data"?>
><data>...</data>
>
>Kind regards,
>Mats
>
>
>PS. Pity that native XML standards support seems to be degrading in browsers...
>
>
>
>
>________________________________
>
>

Re: [Xsltforms-support] odd behaviour, or a big: Select1 inside a Repeat

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

Hello Habs,

I have not reproduced this issue with the attached test case.

Could you please send me another test case?

Thanks!

-Alain

Le 02/05/2014 15:05, Chris H. a écrit :
> Hello folks, good day to all
>
> Ive posted details on the 'discussion' forum.  Initially, Im wanting 
> to know if this is a bug or not please ? - it certainly is something 
> i've not noticed previously.
>
> https://sourceforge.net/p/xsltforms/discussion/878084/thread/27c2f911/
>
> Thanks
> Habs
>

Re: [Xsltforms-support] Booting XsltForms from an instance data document

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

Hi Mats,

Because the document() function is not allowed by Chrome, I had to force 
the Profiler into the stylesheet itself...

Could please you try with another browser?

Is it an important feature for you? This could be rewritten with 
Javascript (and native XSLT engine launched with Javascript). What do 
you think?

Thanks!

-Alain

Le 04/05/2014 11:52, Mats Eklund a écrit :
> Hi Alain,
>
> I tried the ?xml-form approach, however, the resulting page is an 
> XSLTForms Profiler page rather than the form!? Am I doing something 
> wrong then?
>
> My xml file looks like this:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
> <?xml-form type="application/xhtml+xml" href="myform.xhtml" 
> instance="data"?>
> <data>...</data>
>
> Kind regards,
> Mats
>
> PS. Pity that native XML standards support seems to be degrading in 
> browsers...
>
> ------------------------------------------------------------------------
>

Re: [Xsltforms-support] Booting XsltForms from an instance data document

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

Hi Alain,

I tried the ?xml-form approach, however, the resulting page is an XSLTForms Profiler page rather than the form!? Am I doing something wrong then? 

My xml file looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xml-form type="application/xhtml+xml" href="myform.xhtml" instance="data"?>
<data>...</data>

Kind regards,
Mats


PS. Pity that native XML standards support seems to be degrading in browsers...



________________________________
 From: Alain Couthures <ala...@ag...>
To: Mats Eklund <mat...@ya...>; "xsl...@li..." <xsl...@li...> 
Sent: Sunday, May 4, 2014 10:02 AM
Subject: Re: [Xsltforms-support] Booting XsltForms from an instance data document
 


Hi Mats,

Yes, XSLTForms stylesheet is looking for a processing instruction
      to load a specified form with the associated instance as the
      default one
      (http://lists.w3.org/Archives/Public/public-forms/2011Oct/0026.html). So, 2 processing instructions are required: one for xsltforms.xsl, one for the form to be loaded.

Unfortunately, document() use is locally forbidden in Chrome,
      native XSLT support is compromised in future browser versions...
      As a workaround for XSLTFoms 2.0, the SCRIPT HTML element seems to
      be the unique possibility to emulate processing instructions (the
      instance should be embedded into a script/@type="text/xml"
      element).

Thank you for your feedback!

-Alain


Le 03/05/2014 08:41, Mats Eklund a écrit :

Hi,
>
>I am experimenting with the idea to be able to open an instance
        data document in the browser and have it load with an associated
        xforms document. I am thinking this could be done using a
        2-stage XSLT transformation, where the first transformation
        inserts the opened instance data document into the default data
        instance of its associated xforms document (specified as a
        parameter in a processing instruction), and then let the
        resulting document be the input for the second transformation -
        the XsltForms stylesheet - to have the form rendered in the
        browser.
>
>Does the XsltForms stylesheet has any provisions for this
        approach already? I was able to achieve the desired result by
        rewriting some of the templates and xpath expressions in the
        xsltforms stylesheet (including rewiring references to root node
        to root node of the result document of the first
        transformation), but would prefer not to do much changes to the
        XsltForms stylesheet.
>
>Kind regards,
>Mats
>
>

Re: [Xsltforms-support] Problems when using Chrome 34 and Opera 12

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

Thanks Alain,

I downloaded latest revision and got it working in Chrome 34!

I think your approach makes sense, however, I think it is a pity that the only way of loading would be via Javascript and not via the XML processing instruction.

Kind regards,
Mats




________________________________
 From: Alain Couthures <ala...@ag...>
To: Mats Eklund <mat...@ya...>; "xsl...@li..." <xsl...@li...> 
Sent: Sunday, May 4, 2014 9:28 AM
Subject: Re: [Xsltforms-support] Problems when using Chrome 34 and Opera 12
 


Hi Mats,

I suspect that this is not the same issue with Chrome and with
      Opera.

Chrome 34 has anticipated DOM4: attributes are not nodes anymore,
      it is not possible to get the corresponding owner element,
      namespace declarations are treated as regular attributes,...
      Latest revision of XSLTForms, only in source repositories, has
      some workarounds for this. At least, there is no exception...

Opera does not allow loading of local XSLT stylesheet (with file:// protocol). It sounds to be a security restriction but other browser vendors don't seem to follow this...

Actually, the use of native implementations of W3C standards in
      XSLTForms is a weak point: Google team is eager to remove its XSLT
      engine from Chrome, DOM4 is lighter than DOM3 and is not enough
      for full XML processing. I am currently working on XSLTForms 2.0:
      it will have its own Javascript DOM3 implementation and it will
      support Javascript-only form loading as a full polyfill.

So, these issues should not be possible with future versions of
      XSLTForms.

What do you think?

-Alain

Le 01/05/2014 07:47, Mats Eklund a écrit :

Hi Alain and others, 
>
>
>I am just beginning to try XsltForms, and am having problems opening my first form in Chrome (v34) and in Opera (v12.17) getting the following error messages:
>
>
>
>Chrome error on loading form:
>
>Javscript Alert
>XSLTForms Exception
>Error dispatching event 'xforms-model-construct'
>TypeError: undefined is not a function 
>
> at Object.XsltForms_browser.getMeta(...xsltforms.js: 1083:474)
> at
XsltForms_coreElement.XsltForms_instance.validate_(...xsltforms.js:7114:34)
>....
>TypeError
>undefined is not a function
>
> 
>Opera error on loading form:
>File not found: file://localhost/C:/.../xsltforms/config_en.xsl
>and subsequently
>XSLTForms Exception
>Error initializing:
><anonymous function: XsltForms_browser.loadNode>([arguments not available])@file://localhost/.../xsltforms.js:894
>...
>TypeError
>Cannot convert 'src' to object
>
>
>
>Are these known problems, and is there a solution? The form loads fine in Firefox!
>
>
>
>Thanks for your support!
>
>
>Mats
>
>
>
>

Re: [Xsltforms-support] Booting XsltForms from an instance data document

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

Hi Mats,

Yes, XSLTForms stylesheet is looking for a processing instruction to 
load a specified form with the associated instance as the default one 
(http://lists.w3.org/Archives/Public/public-forms/2011Oct/0026.html). 
So, 2 processing instructions are required: one for xsltforms.xsl, one 
for the form to be loaded.

Unfortunately, document() use is locally forbidden in Chrome, native 
XSLT support is compromised in future browser versions... As a 
workaround for XSLTFoms 2.0, the SCRIPT HTML element seems to be the 
unique possibility to emulate processing instructions (the instance 
should be embedded into a script/@type="text/xml" element).

Thank you for your feedback!

-Alain

Le 03/05/2014 08:41, Mats Eklund a écrit :
> Hi,
>
> I am experimenting with the idea to be able to open an instance data 
> document in the browser and have it load with an associated xforms 
> document. I am thinking this could be done using a 2-stage XSLT 
> transformation, where the first transformation inserts the opened 
> instance data document into the default data instance of its 
> associated xforms document (specified as a parameter in a processing 
> instruction), and then let the resulting document be the input for the 
> second transformation - the XsltForms stylesheet - to have the form 
> rendered in the browser.
>
> Does the XsltForms stylesheet has any provisions for this approach 
> already? I was able to achieve the desired result by rewriting some of 
> the templates and xpath expressions in the xsltforms stylesheet 
> (including rewiring references to root node to root node of the result 
> document of the first transformation), but would prefer not to do much 
> changes to the XsltForms stylesheet.
>
> Kind regards,
> Mats
>

Re: [Xsltforms-support] Problems when using Chrome 34 and Opera 12

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

Hi Mats,

I suspect that this is not the same issue with Chrome and with Opera.

Chrome 34 has anticipated DOM4: attributes are not nodes anymore, it is 
not possible to get the corresponding owner element, namespace 
declarations are treated as regular attributes,... Latest revision of 
XSLTForms, only in source repositories, has some workarounds for this. 
At least, there is no exception...

Opera does not allow loading of local XSLT stylesheet (with file:// 
protocol). It sounds to be a security restriction but other browser 
vendors don't seem to follow this...

Actually, the use of native implementations of W3C standards in 
XSLTForms is a weak point: Google team is eager to remove its XSLT 
engine from Chrome, DOM4 is lighter than DOM3 and is not enough for full 
XML processing. I am currently working on XSLTForms 2.0: it will have 
its own Javascript DOM3 implementation and it will support 
Javascript-only form loading as a full polyfill.

So, these issues should not be possible with future versions of XSLTForms.

What do you think?

-Alain

Le 01/05/2014 07:47, Mats Eklund a écrit :
> Hi Alain and others,
>
> I am just beginning to try XsltForms, and am having problems opening 
> my first form in Chrome (v34) and in Opera (v12.17) getting the 
> following error messages:
>
> Chrome error on loading form:
> Javscript Alert
> XSLTForms Exception
> Error dispatching event 'xforms-model-construct'
> TypeError: undefined is not a function
>  at Object.XsltForms_browser.getMeta(...xsltforms.js: 1083:474)
>  at 
> XsltForms_coreElement.XsltForms_instance.validate_(...xsltforms.js:7114:34)
> ....
> TypeError
> undefined is not a function
> Opera error on loading form:
> File not found: file://localhost/C:/.../xsltforms/config_en.xsl
> and subsequently
> XSLTForms Exception
> Error initializing:
> <anonymous function: XsltForms_browser.loadNode>([arguments not 
> available])@file://localhost/.../xsltforms.js:894
> ...
> TypeError
> Cannot convert 'src' to object
>
> Are these known problems, and is there a solution? The form loads fine 
> in Firefox!
>
> Thanks for your support!
>
> Mats
>
>
>

[Xsltforms-support] Booting XsltForms from an instance data document

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

Hi,

I am experimenting with the idea to be able to open an instance data document in the browser and have it load with an associated xforms document. I am thinking this could be done using a 2-stage XSLT transformation, where the first transformation inserts the opened instance data document into the default data instance of its associated xforms document (specified as a parameter in a processing instruction), and then let the resulting document be the input for the second transformation - the XsltForms stylesheet - to have the form rendered in the browser.

Does the XsltForms stylesheet has any provisions for this approach already? I was able to achieve the desired result by rewriting some of the templates and xpath expressions in the xsltforms stylesheet (including rewiring references to root node to root node of the result document of the first transformation), but would prefer not to do much changes to the XsltForms stylesheet.

Kind regards,
Mats




________________________________
 From: Mats Eklund <mat...@ya...>
To: "xsl...@li..." <xsl...@li...> 
Sent: Thursday, May 1, 2014 7:47 AM
Subject: Problems when using Chrome 34 and Opera 12
 


Hi Alain and others,


I am just beginning to try XsltForms, and am having problems opening my first form in Chrome (v34) and in Opera (v12.17) getting the following error messages:


Chrome error on loading form:

Javscript Alert
XSLTForms Exception
Error dispatching event 'xforms-model-construct'
TypeError: undefined is not a function 

 at Object.XsltForms_browser.getMeta(...xsltforms.js: 1083:474)
 at XsltForms_coreElement.XsltForms_instance.validate_(...xsltforms.js:7114:34)
....
TypeError
undefined is not a function

 
Opera error on loading form:
File not found: file://localhost/C:/.../xsltforms/config_en.xsl
and subsequently
XSLTForms Exception
Error initializing:
<anonymous function: XsltForms_browser.loadNode>([arguments not available])@file://localhost/.../xsltforms.js:894
...
TypeError
Cannot convert 'src' to object


Are these known problems, and is there a solution? The form loads fine in Firefox!



Thanks for your support!

Mats

[Xsltforms-support] odd behaviour, or a big: Select1 inside a Repeat

[Chris H. <bc...@sh...>]

Hello folks, good day to all

Ive posted details on the 'discussion' forum.  Initially, Im wanting to
know if this is a bug or not please ? - it certainly is something i've not
noticed previously.

https://sourceforge.net/p/xsltforms/discussion/878084/thread/27c2f911/

Thanks
Habs

[Xsltforms-support] Dialog vertical position problems on the last revisions

[Ioan F. <mi...@gm...>]

Hello!

The problem appear on the pages with many positions, with scroll, on 
tabular repeat. Openning an dialog box for editing or adding line, this 
appear somewhere below the page, centered on entire page, not on the 
visible area.

I noticed the trouble on versions 593 and subsequent. The last one I 
used it work properly was 586 and I could not understand what has changed.

I tried various ways of positioning in CSS, but I did not succeed to get 
normal functionality. Please could you give me an idea for solving.

Thanks,
Ioan

Re: [Xsltforms-support] Problems when using Chrome 34 and Opera 12

[Mark B. <ma...@te...>]

Mats

We saw the Chrome problems on the release of Chrome 34 and fixed them by using build 594 - a further problem that we weren’t seeing was fixed by Alain in build 595 (on the source forge site at http://sourceforge.net/p/xsltforms).

The new code is also giving us no errors in Opera 12.

Not sure if the bundled download (xslt-forms-1.0RC@.zip) on Sourceforge is the latest build - we took the files from the repository.

HTH

Mark Barratt

On 1 May 2014, at 06:47, Mats Eklund <mat...@ya...> wrote:

> Hi Alain and others,
> 
> I am just beginning to try XsltForms, and am having problems opening my first form in Chrome (v34) and in Opera (v12.17) getting the following error messages:
> 
> Chrome error on loading form:
> Javscript Alert
> XSLTForms Exception
> Error dispatching event 'xforms-model-construct'
> TypeError: undefined is not a function 
>  at Object.XsltForms_browser.getMeta(...xsltforms.js: 1083:474)
>  at XsltForms_coreElement.XsltForms_instance.validate_(...xsltforms.js:7114:34)
> ....
> TypeError
> undefined is not a function
>  
> Opera error on loading form:
> File not found: file://localhost/C:/.../xsltforms/config_en.xsl
> and subsequently
> XSLTForms Exception
> Error initializing:
> <anonymous function: XsltForms_browser.loadNode>([arguments not available])@file://localhost/.../xsltforms.js:894
> ...
> TypeError
> Cannot convert 'src' to object
> 
> Are these known problems, and is there a solution? The form loads fine in Firefox!
> 
> Thanks for your support!
> 
> Mats
> 
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs_______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] Problems when using Chrome 34 and Opera 12

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

Hi Alain and others,


I am just beginning to try XsltForms, and am having problems opening my first form in Chrome (v34) and in Opera (v12.17) getting the following error messages:


Chrome error on loading form:

Javscript Alert
XSLTForms Exception
Error dispatching event 'xforms-model-construct'
TypeError: undefined is not a function 

 at Object.XsltForms_browser.getMeta(...xsltforms.js: 1083:474)
 at XsltForms_coreElement.XsltForms_instance.validate_(...xsltforms.js:7114:34)
....
TypeError
undefined is not a function

 
Opera error on loading form:
File not found: file://localhost/C:/.../xsltforms/config_en.xsl
and subsequently
XSLTForms Exception
Error initializing:
<anonymous function: XsltForms_browser.loadNode>([arguments not available])@file://localhost/.../xsltforms.js:894
...
TypeError
Cannot convert 'src' to object


Are these known problems, and is there a solution? The form loads fine in Firefox!


Thanks for your support!

Mats

Re: [Xsltforms-support] getInstanceDocument() in Internet Explorer

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

Hi Mark,

Because XSLTForms 1.0 is using native DOM, it is just DOM2 with IE: this 
test case works replacing "alert(my_color.textContent)" by 
"alert(my_color.textContent || my_color.text)".

BTW, I have developed my own DOM implementation written in Javascript 
because DOM4 is inappropriate for XML processing. It will be integrated 
in XSLTForms 2.0.

Thank you for your feedback!

-Alain

Le 22/04/2014 21:22, Mark Seaborne a écrit :
> Hi,
>
> I have a form that uses the getInstanceDocument() function. It works fine in all the browsers I have tried except Internet Explorer versions 8, 9 and 11 (haven't tried 10).
>
> I am using build r595. A test form is provided below. Obviously I can't test if any of the XSLTForms functions for manipulating instances in IE.
>
> Should I be doing something different to get the form working in IE? Any help would be very much appreciated.
>
> Thanks
>
> Mark
>
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
> <?xsltforms-options debug="yes"?>
> <?css-conversion no?>
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events">
>      <head>
>          <title>4.8.1.a getInstanceDocument() method
>              (non-normative)</title>
>          <script type="text/javascript">
>          function init() {
>              var model = document.getElementById('my_model1');
>              var inst1 = model.getInstanceDocument('my_data1');
>              var my_color = inst1.getElementsByTagName('color')[0];
>              alert(my_color.textContent);
>              }
>          </script>
>          <xforms:model id="my_model1">
>              <xforms:instance id="my_data1" xmlns="">
>                  <car>
>                      <color>blue</color>
>                  </car>
>              </xforms:instance>
>          </xforms:model>
>      </head>
>      <body onload="init()">
>          <xforms:group>
>              <xforms:label class="title">4.8.1.a getInstanceDocument()
>                  method (non-normative)</xforms:label>
>          </xforms:group>
>          <xforms:group>
>              <p>
>                  This test case uses Javascript to execute the
>                  getInstanceDocument() method.
>                  You may have seen a message box with the value
>                  &quot;<xforms:output ref="color"/>&quot;.
>              </p>
>          </xforms:group>
>      </body>
> </html>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] getInstanceDocument() in Internet Explorer

[Mark S. <m_s...@me...>]

Hi,

I have a form that uses the getInstanceDocument() function. It works fine in all the browsers I have tried except Internet Explorer versions 8, 9 and 11 (haven't tried 10). 

I am using build r595. A test form is provided below. Obviously I can't test if any of the XSLTForms functions for manipulating instances in IE. 

Should I be doing something different to get the form working in IE? Any help would be very much appreciated.

Thanks

Mark




<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<?css-conversion no?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events">
    <head>
        <title>4.8.1.a getInstanceDocument() method 
            (non-normative)</title>
        <script type="text/javascript">
        function init() {
            var model = document.getElementById('my_model1');
            var inst1 = model.getInstanceDocument('my_data1');
            var my_color = inst1.getElementsByTagName('color')[0];
            alert(my_color.textContent);
            }
        </script>
        <xforms:model id="my_model1">
            <xforms:instance id="my_data1" xmlns="">
                <car>
                    <color>blue</color>
                </car>
            </xforms:instance>
        </xforms:model>
    </head>
    <body onload="init()">
        <xforms:group>
            <xforms:label class="title">4.8.1.a getInstanceDocument() 
                method (non-normative)</xforms:label>
        </xforms:group>
        <xforms:group>
            <p>
                This test case uses Javascript to execute the 
                getInstanceDocument() method.
                You may have seen a message box with the value 
                &quot;<xforms:output ref="color"/>&quot;.
            </p>
        </xforms:group>
    </body>
</html>

Re: [Xsltforms-support] Error on upgrade to Chrome 34

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

Dan,

I have now added a pull request for the demo package too.

Chrome 34 has a modified DOM where "xmlns" is now returned as an 
attribute...

Thank you for your feedback!

-Alain

Le 16/04/2014 19:47, Dan McCreary a écrit :
> Alain,
>
> Thanks again for keeping the eXist XSLTForms demo package up to date 
> to support Chrome version 34!  We are also looking forward to trying 
> the new TinyMCE editor 4.0 features.
>
> I don't know why Chrome 34 is having problems, but it appears that 
> other web sites are also finding that old stable JavaScript code no 
> longer runs on Chrome 34.
>
> - Dan
>
>

Re: [Xsltforms-support] Error on upgrade to Chrome 34

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

Dan,

I have pulled rev.594 to eXist github repository.

Please be aware that latest TinyMCE version is now supported by default: 
2 attributes have to be added (data-uri="http://www.tinymce.com" 
data-version="4.0" or "3.0") to the script tag.

Thank you for your feedbacks!

-Alain

Le 16/04/2014 17:15, Dan McCreary a écrit :
> I did a little further testing about the XSLTForms demos in the eXist 
> package not working on the latest version of Chrome 34.
>
> When I access the XForms demos on Alain's web site here:
>
> (http://www.agencexml.com/xsltforms)  with Chrome 34, which I *think* 
> is running reversion 594 of xsltforms.js all of the example seem to 
> run without any errors.
>
> Here is the path to that file which currently says "Rev. 594" on the 
> first line of that file.
>
> http://www.agencexml.com/xsltforms/xsltforms/xsltforms.js
>
> When I copied this version of version /xsltforms.js 594 to the eXist 
> examples (which was running an older version called 1.0RC2) things 
> seem to work OK on Chrome 34.
>
> I will be glad to update the eXist package if anyone wants to walk me 
> through the steps.
>
> Thanks - Dan
>
>
> On Wed, Apr 16, 2014 at 9:37 AM, Dan McCreary <dan...@gm... 
> <mailto:dan...@gm...>> wrote:
>
>     I just loaded the eXist demo application and I am getting a popup
>     error on Chrome 34 error also.
>
>     This happens for every character I type into the input field.
>
>     Any suggestions would be appreciated.
>
>     Thanks! - Dan
>
>     Inline image 1
>
>
>     On Tue, Apr 15, 2014 at 8:46 AM, Mark Barratt
>     <ma...@te... <mailto:ma...@te...>> wrote:
>
>         Hi Alain
>
>         Well...
>
>         Most or all of the forms on your site examples page
>         http://www.agencexml.com/xsltforms fail with the same/similar
>         errors in Chrome 34 on Mac and Windows for me and my
>         colleagues and our client (who uses some prehistoric Windows
>         version).
>
>         You are seeing these load without error?
>
>         best
>
>         Mark
>
>         On 10 Apr 2014, at 20:23, Alain Couthures
>         <ala...@ag...
>         <mailto:ala...@ag...>> wrote:
>
>         > Hello Mark,
>         >
>         > Because I cannot see such an error with version 1.0RC2 and
>         Chrome 34, I think that you should give it a try!
>         >
>         > Thank you for your feedback!
>         >
>         > -Alain
>         >
>         > Le 10/04/2014 13:22, Mark Barratt a écrit :
>         >> Using R557 of the framework (because it works - well, up to
>         now).
>         >>
>         >> On upgrading to Chrome 34 from 33 we get a popup error on
>         both Mac and Windows:
>         >>
>         >> XSLTForms Exception
>         >>
>         >> Error dispatching event 'xforms-model-construct' :
>         >>
>         >> TypeError: undefined is not a function
>         >>     at Object.XsltForms_browser.getMeta
>         (http://mysite.org/static/xsltforms/xsltforms.js:1491:242)
>         >>     at XsltForms_coreElement.XsltForms_instance.validate_
>         (http://mysite.org/static/xsltforms/xsltforms.js:3235:34)
>         >>     at XsltForms_coreElement.XsltForms_instance.validation_
>         (http://mysite.org/static/xsltforms/xsltforms.js:3211:7)
>         >>     at XsltForms_coreElement.XsltForms_instance.validation_
>         (http://mysite.org/static/xsltforms/xsltforms.js:3223:9)
>         >>     at XsltForms_coreElement.XsltForms_instance.revalidate
>         (http://mysite.org/static/xsltforms/xsltforms.js:3200:8)
>         >>     at Object.XsltForms_browser.forEach
>         (http://mysite.org/static/xsltforms/xsltforms.js:2318:12)
>         >>     at XsltForms_coreElement.XsltForms_model.revalidate
>         (http://mysite.org/static/xsltforms/xsltforms.js:2978:20)
>         >>     at XsltForms_coreElement.XsltForms_model.recalculate
>         (http://mysite.org/static/xsltforms/xsltforms.js:2970:8)
>         >>     at XsltForms_coreElement.XsltForms_model.rebuild
>         (http://mysite.org/static/xsltforms/xsltforms.js:2958:8)
>         >>     at XsltForms_coreElement.XsltForms_model.rebuild
>         (http://mysite.org/static/xsltforms/xsltforms.js:2930:8)
>         >>
>         >> Anyone else seen this or similar on Chrome 34? Any reason
>         to believe that upgrading to current framework would stop it
>         happening?
>         >>
>         >> Thanks
>         >>
>         >> --
>         >> Mark Barratt
>         >>
>         >>
>         ------------------------------------------------------------------------------
>         >> Put Bad Developers to Shame
>         >> Dominate Development with Jenkins Continuous Integration
>         >> Continuously Automate Build, Test & Deployment
>         >> Start a new project now. Try Jenkins in the cloud.
>         >> http://p.sf.net/sfu/13600_Cloudbees
>         >> _______________________________________________
>         >> Xsltforms-support mailing list
>         >> Xsl...@li...
>         <mailto:Xsl...@li...>
>         >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>         >>
>         >
>
>         --
>         Mark Barratt
>         Text Matters
>
>         We help explain things using design | language | systems |
>         process improvement
>
>         ma...@te... <mailto:ma...@te...> | +44
>         (0)118 986 8313 <tel:%2B44%20%280%29118%20986%208313>
>         http://www.textmatters.com | Twitter @mark_barratt | Skype
>         mark_barratt
>
>
>
>
>         ------------------------------------------------------------------------------
>         Learn Graph Databases - Download FREE O'Reilly Book
>         "Graph Databases" is the definitive new guide to graph
>         databases and their
>         applications. Written by three acclaimed leaders in the field,
>         this first edition is now available. Download your free book
>         today!
>         http://p.sf.net/sfu/NeoTech
>         _______________________________________________
>         Xsltforms-support mailing list
>         Xsl...@li...
>         <mailto:Xsl...@li...>
>         https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
>     -- 
>     Dan McCreary
>     http://danmccreary.com
>     Co-author: Making Sense of NoSQL <http://manning.com/mccreary>
>     office: (952) 931-9198 <tel:%28952%29%20931-9198>
>     cell: (612) 986-1552 <tel:%28612%29%20986-1552>
>     skype: dmccreary47
>
>
>
>
> -- 
> Dan McCreary
> http://danmccreary.com
> Co-author: Making Sense of NoSQL <http://manning.com/mccreary>
> office: (952) 931-9198
> cell: (612) 986-1552
> skype: dmccreary47

Re: [Xsltforms-support] Error on upgrade to Chrome 34

[Mark B. <ma...@te...>]

Hi Alain

Well…

Most or all of the forms on your site examples page http://www.agencexml.com/xsltforms fail with the same/similar errors in Chrome 34 on Mac and Windows for me and my colleagues and our client (who uses some prehistoric Windows version).

You are seeing these load without error?

best

Mark

On 10 Apr 2014, at 20:23, Alain Couthures <ala...@ag...> wrote:

> Hello Mark,
> 
> Because I cannot see such an error with version 1.0RC2 and Chrome 34, I think that you should give it a try!
> 
> Thank you for your feedback!
> 
> -Alain
> 
> Le 10/04/2014 13:22, Mark Barratt a écrit :
>> Using R557 of the framework (because it works - well, up to now).
>> 
>> On upgrading to Chrome 34 from 33 we get a popup error on both Mac and Windows:
>> 
>> XSLTForms Exception
>> 
>> Error dispatching event 'xforms-model-construct' :
>> 
>> TypeError: undefined is not a function
>>     at Object.XsltForms_browser.getMeta (http://mysite.org/static/xsltforms/xsltforms.js:1491:242)
>>     at XsltForms_coreElement.XsltForms_instance.validate_ (http://mysite.org/static/xsltforms/xsltforms.js:3235:34)
>>     at XsltForms_coreElement.XsltForms_instance.validation_ (http://mysite.org/static/xsltforms/xsltforms.js:3211:7)
>>     at XsltForms_coreElement.XsltForms_instance.validation_ (http://mysite.org/static/xsltforms/xsltforms.js:3223:9)
>>     at XsltForms_coreElement.XsltForms_instance.revalidate (http://mysite.org/static/xsltforms/xsltforms.js:3200:8)
>>     at Object.XsltForms_browser.forEach (http://mysite.org/static/xsltforms/xsltforms.js:2318:12)
>>     at XsltForms_coreElement.XsltForms_model.revalidate (http://mysite.org/static/xsltforms/xsltforms.js:2978:20)
>>     at XsltForms_coreElement.XsltForms_model.recalculate (http://mysite.org/static/xsltforms/xsltforms.js:2970:8)
>>     at XsltForms_coreElement.XsltForms_model.rebuild (http://mysite.org/static/xsltforms/xsltforms.js:2958:8)
>>     at XsltForms_coreElement.XsltForms_model.rebuild (http://mysite.org/static/xsltforms/xsltforms.js:2930:8)
>> 
>> Anyone else seen this or similar on Chrome 34? Any reason to believe that upgrading to current framework would stop it happening?
>> 
>> Thanks
>> 
>> --
>> Mark Barratt
>> 
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>> 
> 

--
Mark Barratt
Text Matters

We help explain things using design | language | systems | process improvement

ma...@te... | +44 (0)118 986 8313
http://www.textmatters.com | Twitter @mark_barratt | Skype mark_barratt

[Xsltforms-support] Support for ref attribute in label elements

[Isidro V. V. <jv...@gm...>]

Hi,

I am trying to get use the ref attribute in a label element but 
apparently it doesn't seems to work.

                 <xf:repeat nodeset="Customers">
                   <tr>
                     <td>
                       <xf:trigger>
                         <xf:label ref="CustomerName"/>
                       </xf:trigger>
                     </td>
                     ...
                   </tr>
                 </xf:repeat>

According to specification 
(http://www.w3.org/TR/xforms11/#ui-commonelems-label) it should be 
possible, but I would like to ask Alan if it is implemented or if anyone 
has used it

Thanks

Isidro

Re: [Xsltforms-support] TinyMCE

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

Hi Mark,

Unfortunately, Apple decided not to provide Windows version of Safari 
after 5.1.7. I am not able to reproduce this issue but I think that some 
try/catch could fix this...

This example at agencexml.com is currently using TinyMCE 3.4.6. You 
could try this very same example form with a more recent TinyMCE 3.x 
version.

With rev.593, TinyMCE 4.0 is now also supported. Two attributes have to 
be added at the script element to identify it: 
data-uri="http://www.tinymce.com" and data-version="4.0". Please find 
attached a test form.

Thank you for your feedback!

-Alain

Le 09/04/2014 23:30, Mark Lawson a écrit :
> Hi,
>
> I’m getting an odd error with the TinyMCE example at http://www.agencexml.com/xsltforms/tinymce.xml
>
> When I load it into Safari 7.03 I get the following :
>
> TypeError: 'null' is not an object (evaluating 's.getRng')
>
> If I dismiss the alert, everything works ok though. Any ideas?
>
> Rgds,
>
> Mark Lawson
>
>
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Error on upgrade to Chrome 34

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

Hello Mark,

Because I cannot see such an error with version 1.0RC2 and Chrome 34, I 
think that you should give it a try!

Thank you for your feedback!

-Alain

Le 10/04/2014 13:22, Mark Barratt a écrit :
> Using R557 of the framework (because it works - well, up to now).
>
> On upgrading to Chrome 34 from 33 we get a popup error on both Mac and Windows:
>
> XSLTForms Exception
>
> Error dispatching event 'xforms-model-construct' :
>
> TypeError: undefined is not a function
>      at Object.XsltForms_browser.getMeta (http://mysite.org/static/xsltforms/xsltforms.js:1491:242)
>      at XsltForms_coreElement.XsltForms_instance.validate_ (http://mysite.org/static/xsltforms/xsltforms.js:3235:34)
>      at XsltForms_coreElement.XsltForms_instance.validation_ (http://mysite.org/static/xsltforms/xsltforms.js:3211:7)
>      at XsltForms_coreElement.XsltForms_instance.validation_ (http://mysite.org/static/xsltforms/xsltforms.js:3223:9)
>      at XsltForms_coreElement.XsltForms_instance.revalidate (http://mysite.org/static/xsltforms/xsltforms.js:3200:8)
>      at Object.XsltForms_browser.forEach (http://mysite.org/static/xsltforms/xsltforms.js:2318:12)
>      at XsltForms_coreElement.XsltForms_model.revalidate (http://mysite.org/static/xsltforms/xsltforms.js:2978:20)
>      at XsltForms_coreElement.XsltForms_model.recalculate (http://mysite.org/static/xsltforms/xsltforms.js:2970:8)
>      at XsltForms_coreElement.XsltForms_model.rebuild (http://mysite.org/static/xsltforms/xsltforms.js:2958:8)
>      at XsltForms_coreElement.XsltForms_model.rebuild (http://mysite.org/static/xsltforms/xsltforms.js:2930:8)
>
> Anyone else seen this or similar on Chrome 34? Any reason to believe that upgrading to current framework would stop it happening?
>
> Thanks
>
> --
> Mark Barratt
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>