xsltforms-support Mailing List for XSLTForms
Brought to you by:
alain-couthures
You can subscribe to this list here.
| 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
(2) |
Dec
(1) |
| 2026 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Alain C. <ala...@ag...> - 2026-11-07 14:21:32
|
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div class="default-style" style="">Hello,</div> <div class="default-style" style=""> </div> <div class="default-style" style="">Because XSLT 1.0 will soon be removed from Chromium-based browsers, there is now a Javascript bootstrap for XSLTForms, named `xsltforms-xsl.js` to replace the processing instructions.</div> <div class="default-style" style=""> </div> <div class="default-style" style=""> Depending on the file location, this is the new bootstrap: <br> <br> </div> <div class="default-style" style=""> <div> <!DOCTYPE html><script src="xsltforms-xsl.js"></script><plaintext></div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">Online test files on agenceXML website are being edited progressively.</div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">Have a look at page source: view-source:https://www.agencexml.com/xsltforms/hello.html</div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">XSLTForms 1.8 will be released soon with this bootstrap.</div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">If anyone is in a hurry, please contact me.</div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">Best regards,</div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;"> </div> <div class="default-style" style="font-family: -apple-system, BlinkMacSystemFont, helvetica, sans-serif;">--Alain</div> </div> </body> </html> |
|
From: Josselin M. <mor...@gm...> - 2026-07-02 16:11:24
|
Hi Alain,
It works perfectly. Thanks a lot!
Best,
Josselin
> Le 1 juil. 2026 à 16:27, Alain Couthures <ala...@ag...> a écrit :
>
> Hi Josselin,
>
> Could you please try again with the following XPath expression?
> "event('response-headers')/self::*[name='content-location']/value"
>
> Thank you for your feedback!
>
> --Alain
>
>> Le 26/06/2026 11:13 CEST, Josselin Morvan <mor...@gm...> a écrit :
>>
>>
>> Hi Steven,
>> My apologies, I gave several examples, which might be confusing, but they are present in <xf:resource value="event('response-headers')//[name=‘content-location']/value»/>(the cause of the error)
>> Best,
>> Josselin
>>
>>> Le 26 juin 2026 à 10:44, Steven Pemberton <ste...@cw...> a écrit :
>>>
>>>
>>> you're missing the "//" before the "[":
>>>
>>> Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
>>>
>>>
>>> Steven
>>>
>>> On Thursday 25 June 2026 16:56:00 (+02:00), Josselin Morvan wrote:
>>>
>>>
>>>> Hi Steven,
>>>> Thank you for your help and your suggestion (which I already looked at). Unfortunately, XSLTForms 1.7 returns an error:
>>>>
>>>> XSLTForms Exception
>>>> --------------------------
>>>>
>>>> Error parsing the following XPath expression:
>>>>
>>>> event('response-headers')//[name='content-location']/value
>>>>
>>>> Unexpected character at '[name='content-location']/value’
>>>>
>>>> Here is my code
>>>>
>>>> <xf:action ev:event="xforms-submit-done">
>>>> <xf:message level="modal">
>>>> La ressource a été enregistrée !
>>>> Status : <xf:output value="event('response-status-code')"/>;
>>>> URI : <xf:output value="event('resource-uri')"/>;
>>>> Headers : <xf:output value="event('response-headers')"/>;
>>>> Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
>>>> Reason : <xf:output value="event('response-reason-phrase')"/>;
>>>> Body : <xf:output value="event('response-body')"/>.
>>>> </xf:message>
>>>> <xf:load show="replace" replace="instance">
>>>> <!-- <xf:resource value="event('response-body')//*:url"/> -->
>>>> <xf:resource value="event('response-headers')//[name=‘content-location']/value"/>
>>>> </xf:load>
>>>> </xf:action>
>>>>
>>>> I also tried <xf:resource value="event('response-headers')//*[name=‘content-location']/value" />but without success.
>>>>
>>>> Likewise, <xf:output value="event('response-headers')[name='content-location']/value"/>always returns the value of content-language. If I remove the content-language from my response, it always returns the content-length, not my location.
>>>> <GraphiqueCollé-1.png>
>>>>
>>>> Best,
>>>> Josselin
>>>>
>>>>
>>>>> Le 25 juin 2026 à 13:23, Steven Pemberton via Xsltforms-support <xsl...@li...> a écrit :
>>>>>
>>>>>
>>>>> I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced
>>>>>
>>>>> Chapter "Last modified".
>>>>>
>>>>> What you need is along the lines of
>>>>>
>>>>> <setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/>
>>>>>
>>>>> Best wishes,
>>>>>
>>>>> Steven
>>>>>
>>>>> On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote:
>>>>>
>>>>>
>>>>>> Hi Alain, hi everyone,
>>>>>>
>>>>>> First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
>>>>>>
>>>>>> I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
>>>>>>
>>>>>> He is a minimal example:
>>>>>>
>>>>>> My endpoint returns the following response:
>>>>>>
>>>>>> update:output((
>>>>>> <rest:response>
>>>>>> <http:responsestatus="201"message="Created">
>>>>>> <http:headername="Content-Language"value="fr"/>
>>>>>> <http:headername="Content-Type"value="application/xml; charset=utf-8"/>
>>>>>> <http:headername="Content-Location"value="{'/synopsx-beta/users/'||$name}"/>
>>>>>> </http:response>
>>>>>> </rest:response>,
>>>>>> <result>
>>>>>> <message>Le nouvel utilisateur a été créé.</message>
>>>>>> <user>
>>>>>> <username>{$name}</username>
>>>>>> <!-- add other infos if needed -->
>>>>>> </user>
>>>>>> <url>{'/synopsx-beta/users/' || $name}</url>
>>>>>> </result>
>>>>>> ))
>>>>>>
>>>>>> The `Content-Location` header seems to be ok (from my browser point of view ;))
>>>>>>
>>>>>> <GraphiqueCollé-2.png>
>>>>>>
>>>>>> But I can get only the first one (Content-Language)
>>>>>> I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
>>>>>>
>>>>>> By example:
>>>>>> <xf:outputvalue="event('response-headers')[name='content-location']/value"/>
>>>>>> <xf:outputvalue="event('response-headers')[3]"/>
>>>>>> <xf:outputvalue="event('response-headers')//*:header[*:name=‘content-location’]"/>
>>>>>>
>>>>>> But none of them work. Is someone note something I’m missing ?
>>>>>>
>>>>>> Kind regards,
>>>>>> Josselin
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xsltforms-support mailing list
>>>>>> Xsl...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>>
>>>>> _______________________________________________
>>>>> Xsltforms-support mailing list
>>>>> Xsl...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>
>>
>> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Alain C. <ala...@ag...> - 2026-07-01 14:40:29
|
Hi Josselin,
Could you please try again with the following XPath expression?
"event('response-headers')/self::*[name='content-location']/value"
Thank you for your feedback!
--Alain
> Le 26/06/2026 11:13 CEST, Josselin Morvan <mor...@gm...> a écrit :
>
>
> Hi Steven,
> My apologies, I gave several examples, which might be confusing, but they are present in <xf:resource value="event('response-headers')//[name=‘content-location']/value»/>(the cause of the error)
> Best,
> Josselin
>
> > Le 26 juin 2026 à 10:44, Steven Pemberton <ste...@cw...> a écrit :
> >
> >
> > you're missing the "//" before the "[":
> >
> > Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
> >
> >
> > Steven
> >
> > On Thursday 25 June 2026 16:56:00 (+02:00), Josselin Morvan wrote:
> >
> >
> > > Hi Steven,
> > > Thank you for your help and your suggestion (which I already looked at). Unfortunately, XSLTForms 1.7 returns an error:
> > >
> > > XSLTForms Exception
> > > --------------------------
> > >
> > > Error parsing the following XPath expression:
> > >
> > > event('response-headers')//[name='content-location']/value
> > >
> > > Unexpected character at '[name='content-location']/value’
> > >
> > > Here is my code
> > >
> > > <xf:action ev:event="xforms-submit-done">
> > > <xf:message level="modal">
> > > La ressource a été enregistrée !
> > > Status : <xf:output value="event('response-status-code')"/>;
> > > URI : <xf:output value="event('resource-uri')"/>;
> > > Headers : <xf:output value="event('response-headers')"/>;
> > > Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
> > > Reason : <xf:output value="event('response-reason-phrase')"/>;
> > > Body : <xf:output value="event('response-body')"/>.
> > > </xf:message>
> > > <xf:load show="replace" replace="instance">
> > > <!-- <xf:resource value="event('response-body')//*:url"/> -->
> > > <xf:resource value="event('response-headers')//[name=‘content-location']/value"/>
> > > </xf:load>
> > > </xf:action>
> > >
> > > I also tried <xf:resource value="event('response-headers')//*[name=‘content-location']/value" />but without success.
> > >
> > > Likewise, <xf:output value="event('response-headers')[name='content-location']/value"/>always returns the value of content-language. If I remove the content-language from my response, it always returns the content-length, not my location.
> > > <GraphiqueCollé-1.png>
> > >
> > > Best,
> > > Josselin
> > >
> > >
> > > > Le 25 juin 2026 à 13:23, Steven Pemberton via Xsltforms-support <xsl...@li...> a écrit :
> > > >
> > > >
> > > > I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced
> > > >
> > > > Chapter "Last modified".
> > > >
> > > > What you need is along the lines of
> > > >
> > > > <setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/>
> > > >
> > > > Best wishes,
> > > >
> > > > Steven
> > > >
> > > > On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote:
> > > >
> > > >
> > > > > Hi Alain, hi everyone,
> > > > >
> > > > > First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
> > > > >
> > > > > I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
> > > > >
> > > > > He is a minimal example:
> > > > >
> > > > > My endpoint returns the following response:
> > > > >
> > > > > update:output((
> > > > > <rest:response>
> > > > > <http:responsestatus="201"message="Created">
> > > > > <http:headername="Content-Language"value="fr"/>
> > > > > <http:headername="Content-Type"value="application/xml; charset=utf-8"/>
> > > > > <http:headername="Content-Location"value="{'/synopsx-beta/users/'||$name}"/>
> > > > > </http:response>
> > > > > </rest:response>,
> > > > > <result>
> > > > > <message>Le nouvel utilisateur a été créé.</message>
> > > > > <user>
> > > > > <username>{$name}</username>
> > > > > <!-- add other infos if needed -->
> > > > > </user>
> > > > > <url>{'/synopsx-beta/users/' || $name}</url>
> > > > > </result>
> > > > > ))
> > > > >
> > > > > The `Content-Location` header seems to be ok (from my browser point of view ;))
> > > > >
> > > > > <GraphiqueCollé-2.png>
> > > > >
> > > > > But I can get only the first one (Content-Language)
> > > > > I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
> > > > >
> > > > > By example:
> > > > > <xf:outputvalue="event('response-headers')[name='content-location']/value"/>
> > > > > <xf:outputvalue="event('response-headers')[3]"/>
> > > > > <xf:outputvalue="event('response-headers')//*:header[*:name=‘content-location’]"/>
> > > > >
> > > > > But none of them work. Is someone note something I’m missing ?
> > > > >
> > > > > Kind regards,
> > > > > Josselin
> > > > >
> > > > > _______________________________________________
> > > > > Xsltforms-support mailing list
> > > > > Xsl...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> > > > >
> > > > _______________________________________________
> > > > Xsltforms-support mailing list
> > > > Xsl...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> > >
>
> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Josselin M. <mor...@gm...> - 2026-06-26 09:14:04
|
Hi Steven,
My apologies, I gave several examples, which might be confusing, but they are present in <xf:resource value="event('response-headers')//[name=‘content-location']/value »/> (the cause of the error)
Best,
Josselin
> Le 26 juin 2026 à 10:44, Steven Pemberton <ste...@cw...> a écrit :
>
> you're missing the "//" before the "[":
>
> Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
>
> Steven
>
> On Thursday 25 June 2026 16:56:00 (+02:00), Josselin Morvan wrote:
>
> Hi Steven,
> Thank you for your help and your suggestion (which I already looked at). Unfortunately, XSLTForms 1.7 returns an error:
>
> XSLTForms Exception
> --------------------------
>
> Error parsing the following XPath expression:
>
> event('response-headers')//[name='content-location']/value
>
> Unexpected character at '[name='content-location']/value’
>
> Here is my code
>
> <xf:action ev:event="xforms-submit-done">
> <xf:message level="modal">
> La ressource a été enregistrée !
> Status : <xf:output value="event('response-status-code')"/>;
> URI : <xf:output value="event('resource-uri')"/>;
> Headers : <xf:output value="event('response-headers')"/>;
> Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
> Reason : <xf:output value="event('response-reason-phrase')"/>;
> Body : <xf:output value="event('response-body')"/>.
> </xf:message>
> <xf:load show="replace" replace="instance">
> <!-- <xf:resource value="event('response-body')//*:url"/> -->
> <xf:resource value="event('response-headers')//[name=‘content-location']/value"/>
> </xf:load>
> </xf:action>
>
> I also tried <xf:resource value="event('response-headers')//*[name=‘content-location']/value" /> but without success.
>
> Likewise, <xf:output value="event('response-headers')[name='content-location']/value"/> always returns the value of content-language. If I remove the content-language from my response, it always returns the content-length, not my location.
> <GraphiqueCollé-1.png>
>
> Best,
> Josselin
>
>
>> Le 25 juin 2026 à 13:23, Steven Pemberton via Xsltforms-support <xsl...@li...> a écrit :
>>
>> I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced
>>
>> Chapter "Last modified".
>>
>> What you need is along the lines of
>>
>> <setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/>
>>
>> Best wishes,
>>
>> Steven
>>
>> On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote:
>>
>> Hi Alain, hi everyone,
>>
>> First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
>>
>> I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
>>
>> He is a minimal example:
>>
>> My endpoint returns the following response:
>>
>> update:output((
>> <rest:response>
>> <http:response status="201" message="Created">
>> <http:header name="Content-Language" value="fr"/>
>> <http:header name="Content-Type" value="application/xml; charset=utf-8"/>
>> <http:header name="Content-Location" value="{'/synopsx-beta/users/' || $name}"/>
>> </http:response>
>> </rest:response>,
>> <result>
>> <message>Le nouvel utilisateur a été créé.</message>
>> <user>
>> <username>{$name}</username>
>> <!-- add other infos if needed -->
>> </user>
>> <url>{'/synopsx-beta/users/' || $name}</url>
>> </result>
>> ))
>>
>> The `Content-Location` header seems to be ok (from my browser point of view ;))
>>
>> <GraphiqueCollé-2.png>
>>
>> But I can get only the first one (Content-Language)
>> I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
>>
>> By example:
>> <xf:output value="event('response-headers')[name='content-location']/value"/>
>> <xf:output value="event('response-headers')[3]"/>
>> <xf:output value="event('response-headers')//*:header[*:name=‘content-location’]"/>
>>
>> But none of them work. Is someone note something I’m missing ?
>>
>> Kind regards,
>> Josselin
>>
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Steven P. <ste...@cw...> - 2026-06-26 08:44:24
|
you're missing the "//" before the "[":
Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
Steven
On Thursday 25 June 2026 16:56:00 (+02:00), Josselin Morvan wrote:
Hi Steven,
Thank you for your help and your suggestion (which I already looked at). Unfortunately, XSLTForms 1.7 returns an error:
XSLTForms Exception
--------------------------
Error parsing the following XPath expression:
event('response-headers')//[name='content-location']/value
Unexpected character at '[name='content-location']/value’
Here is my code
<xf:action ev:event="xforms-submit-done">
<xf:message level="modal">
La ressource a été enregistrée !
Status : <xf:output value="event('response-status-code')"/>;
URI : <xf:output value="event('resource-uri')"/>;
Headers : <xf:output value="event('response-headers')"/>;
Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
Reason : <xf:output value="event('response-reason-phrase')"/>;
Body : <xf:output value="event('response-body')"/>.
</xf:message>
<xf:load show="replace" replace="instance">
<!-- <xf:resource value="event('response-body')//*:url"/> -->
<xf:resource value="event('response-headers')//[name=‘content-location']/value"/>
</xf:load>
</xf:action>
I also tried <xf:resource value="event('response-headers')//*[name=‘content-location']/value" /> but without success.
Likewise, <xf:output value="event('response-headers')[name='content-location']/value"/> always returns the value of content-language. If I remove the content-language from my response, it always returns the content-length, not my location.
[GraphiqueCollé-1.png]
Best,
Josselin
Le 25 juin 2026 à 13:23, Steven Pemberton via Xsltforms-support <xsl...@li...> a écrit :
I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced
Chapter "Last modified".
What you need is along the lines of
<setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/>
Best wishes,
Steven
On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote:
Hi Alain, hi everyone,
First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
He is a minimal example:
My endpoint returns the following response:
update:output((
<rest:response>
<http:response status="201" message="Created">
<http:header name="Content-Language" value="fr"/>
<http:header name="Content-Type" value="application/xml; charset=utf-8"/>
<http:header name="Content-Location" value="{'/synopsx-beta/users/' || $name}"/>
</http:response>
</rest:response>,
<result>
<message>Le nouvel utilisateur a été créé.</message>
<user>
<username>{$name}</username>
<!-- add other infos if needed -->
</user>
<url>{'/synopsx-beta/users/' || $name}</url>
</result>
))
The `Content-Location` header seems to be ok (from my browser point of view ;))
<GraphiqueCollé-2.png>
But I can get only the first one (Content-Language)
I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
By example:
<xf:output value="event('response-headers')[name='content-location']/value"/>
<xf:output value="event('response-headers')[3]"/>
<xf:output value="event('response-headers')//*:header[*:name=‘content-location’]"/>
But none of them work. Is someone note something I’m missing ?
Kind regards,
Josselin
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...
https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Josselin M. <mor...@gm...> - 2026-06-25 14:56:26
|
Hi Steven,
Thank you for your help and your suggestion (which I already looked at). Unfortunately, XSLTForms 1.7 returns an error:
XSLTForms Exception
--------------------------
Error parsing the following XPath expression:
event('response-headers')//[name='content-location']/value
Unexpected character at '[name='content-location']/value’
Here is my code
<xf:action ev:event="xforms-submit-done">
<xf:message level="modal">
La ressource a été enregistrée !
Status : <xf:output value="event('response-status-code')"/>;
URI : <xf:output value="event('resource-uri')"/>;
Headers : <xf:output value="event('response-headers')"/>;
Content-Location : <xf:output value="event('response-headers')[name='content-location']/value"/>;
Reason : <xf:output value="event('response-reason-phrase')"/>;
Body : <xf:output value="event('response-body')"/>.
</xf:message>
<xf:load show="replace" replace="instance">
<!-- <xf:resource value="event('response-body')//*:url"/> -->
<xf:resource value="event('response-headers')//[name=‘content-location']/value"/>
</xf:load>
</xf:action>
I also tried <xf:resource value="event('response-headers')//*[name=‘content-location']/value" /> but without success.
Likewise, <xf:output value="event('response-headers')[name='content-location']/value"/> always returns the value of content-language. If I remove the content-language from my response, it always returns the content-length, not my location.

Best,
Josselin
> Le 25 juin 2026 à 13:23, Steven Pemberton via Xsltforms-support <xsl...@li...> a écrit :
>
> I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced
>
> Chapter "Last modified".
>
> What you need is along the lines of
>
> <setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/>
>
> Best wishes,
>
> Steven
>
> On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote:
>
> Hi Alain, hi everyone,
>
> First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
>
> I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
>
> He is a minimal example:
>
> My endpoint returns the following response:
>
> update:output((
> <rest:response>
> <http:response status="201" message="Created">
> <http:header name="Content-Language" value="fr"/>
> <http:header name="Content-Type" value="application/xml; charset=utf-8"/>
> <http:header name="Content-Location" value="{'/synopsx-beta/users/' || $name}"/>
> </http:response>
> </rest:response>,
> <result>
> <message>Le nouvel utilisateur a été créé.</message>
> <user>
> <username>{$name}</username>
> <!-- add other infos if needed -->
> </user>
> <url>{'/synopsx-beta/users/' || $name}</url>
> </result>
> ))
>
> The `Content-Location` header seems to be ok (from my browser point of view ;))
>
> <GraphiqueCollé-2.png>
>
> But I can get only the first one (Content-Language)
> I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
>
> By example:
> <xf:output value="event('response-headers')[name='content-location']/value"/>
> <xf:output value="event('response-headers')[3]"/>
> <xf:output value="event('response-headers')//*:header[*:name=‘content-location’]"/>
>
> But none of them work. Is someone note something I’m missing ?
>
> Kind regards,
> Josselin
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Steven P. <ste...@cw...> - 2026-06-25 11:45:07
|
I have an example of this in my advanced XForms tutorial at cwi.nl/~steven/xforms/advanced Chapter "Last modified". What you need is along the lines of <setvalue ref="@saved" value="event('response-headers')//[name='last-modified']/value"/> Best wishes, Steven On Thursday 25 June 2026 10:56:01 (+02:00), Josselin Morvan via Xsltforms-support wrote: Hi Alain, hi everyone, First, I realize that I didn’t thank you, Alain, for the last fix about the comment(). I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set. He is a minimal example: My endpoint returns the following response: update:output(( <rest:response> <http:response status="201" message="Created"> <http:header name="Content-Language" value="fr"/> <http:header name="Content-Type" value="application/xml; charset=utf-8"/> <http:header name="Content-Location" value="{'/synopsx-beta/users/' || $name}"/> </http:response> </rest:response>, <result> <message>Le nouvel utilisateur a été créé.</message> <user> <username>{$name}</username> <!-- add other infos if needed --> </user> <url>{'/synopsx-beta/users/' || $name}</url> </result> )) The `Content-Location` header seems to be ok (from my browser point of view ;)) [GraphiqueCollé-2.png] But I can get only the first one (Content-Language) I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html> By example: <xf:output value="event('response-headers')[name='content-location']/value"/> <xf:output value="event('response-headers')[3]"/> <xf:output value="event('response-headers')//*:header[*:name=‘content-location’]"/> But none of them work. Is someone note something I’m missing ? Kind regards, Josselin _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Josselin M. <jos...@ic...> - 2026-06-25 09:12:44
|
Hi Alain, hi everyone,
First, I realize that I didn’t thank you, Alain, for the last fix about the comment().
I'm having an issue with the event('response-header'). It seems that I can retrieve only the first node of the node-set.
He is a minimal example:
My endpoint returns the following response:
update:output((
<rest:response>
<http:response status="201" message="Created">
<http:header name="Content-Language" value="fr"/>
<http:header name="Content-Type" value="application/xml; charset=utf-8"/>
<http:header name="Content-Location" value="{'/synopsx-beta/users/' || $name}"/>
</http:response>
</rest:response>,
<result>
<message>Le nouvel utilisateur a été créé.</message>
<user>
<username>{$name}</username>
<!-- add other infos if needed -->
</user>
<url>{'/synopsx-beta/users/' || $name}</url>
</result>
))
The `Content-Location` header seems to be ok (from my browser point of view ;))

But I can get only the first one (Content-Language)
I tried many solutions suggested here <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-submit-done_Event> and here <https://lists.w3.org/Archives/Public/public-xformsusers/2021Mar/0006.html>
By example:
<xf:output value="event('response-headers')[name='content-location']/value"/>
<xf:output value="event('response-headers')[3]"/>
<xf:output value="event('response-headers')//*:header[*:name=‘content-location’]"/>
But none of them work. Is someone note something I’m missing ?
Kind regards,
Josselin
|
|
From: Alain C. <ala...@ag...> - 2026-01-18 15:34:27
|
Hi Josselin,
Thank you for pointing at this issue.
Please find a patch for adding comment update support, in XsltForms_browser.setValue method:
if (node.nodeType === Fleur.Node.ATTRIBUTE_NODE || node.nodeType === Fleur.Node.TEXT_NODE) {
node.nodeValue = value;
} else if (XsltForms_browser.isIE && node.innerHTML && !(value instanceof Array)) {
node.innerHTML = XsltForms_browser.escape(value);
} else {
becomes
if (node.nodeType === Fleur.Node.ATTRIBUTE_NODE || node.nodeType === Fleur.Node.TEXT_NODE) {
node.nodeValue = value;
} else if (node.nodeType === Fleur.Node.COMMENT_NODE) {
node.data = value;
} else if (XsltForms_browser.isIE && node.innerHTML && !(value instanceof Array)) {
node.innerHTML = XsltForms_browser.escape(value);
} else {
Kind regards,
--Alain
> Le 13/01/2026 13:43 CET, Josselin Morvan via Xsltforms-support <xsl...@li...> a écrit :
>
>
> Hi Alain, Hi everyone,
>
> First and foremost, I wish you a very happy new year.
>
> I’m trying to add a control to a comment() node, however, even if the field is present, the comment node remains hopelessly empty, when I complete the form. I thought I had already done this in a previous project, but I can't seem to find it.
>
> Does anyone know a workaround ?
>
> Here is a small sample tested with XSLTForms 1.7 and 1.6.
>
> Best
> Josselin
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Josselin M. <jos...@ic...> - 2026-01-13 12:44:07
|
Hi Alain, Hi everyone, First and foremost, I wish you a very happy new year. I’m trying to add a control to a comment() node, however, even if the field is present, the comment node remains hopelessly empty, when I complete the form. I thought I had already done this in a previous project, but I can't seem to find it. Does anyone know a workaround ? Here is a small sample tested with XSLTForms 1.7 and 1.6. Best Josselin |
|
From: Josselin M. <mor...@gm...> - 2025-12-04 19:23:48
|
Hi Alain,
Thank you for the quick fix!
Best,
Josselin
Envoyé de mon iPhone
> Le 30 nov. 2025 à 14:40, Alain Couthures <ala...@ag...> a écrit :
>
> Hi Josselin,
>
> It appears that removeAttributeNS() method does not work as expected in browsers for xml:id because of its namespace.
>
> Please find below a simple workaround for this, in xsltforms.js within XsltForms_delete.prototype.run definition:
>
> if (oldOwnerElement.removeAttributeNS) {
>
> becoming
>
> if (oldOwnerElement.removeAttributeNS && node.namespaceURI !== 'http://www.w3.org/XML/1998/namespace') {
>
> This way, removeAttributeNode() is used instead and it now works correctly for both Chrome and Firefox.
>
> Thank you for your feedback!
>
> --Alain
>
>> Le 27/11/2025 21:02 CET, Josselin Morvan <mor...@gm...> a écrit :
>>
>>
>> Hi Alain, hi everyone,
>> I'm having trouble removing xml:id attributes with XSLTForms.
>> I can insert xml:id attributes, but I cannot delete them using xf:delete.
>> As you can see in the attached example, other attributes are removed correctly, but xml:id attributes are not. Is there something I'm missing?
>> I'm using XSLTForms 1.7, with Firefox and Chrome.
>> Many thanks for you help,
>> Josselin
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Alain C. <ala...@ag...> - 2025-11-30 13:54:28
|
Hi Josselin,
It appears that removeAttributeNS() method does not work as expected in browsers for xml:id because of its namespace.
Please find below a simple workaround for this, in xsltforms.js within XsltForms_delete.prototype.run definition:
if (oldOwnerElement.removeAttributeNS) {
becoming
if (oldOwnerElement.removeAttributeNS && node.namespaceURI !== 'http://www.w3.org/XML/1998/namespace') {
This way, removeAttributeNode() is used instead and it now works correctly for both Chrome and Firefox.
Thank you for your feedback!
--Alain
> Le 27/11/2025 21:02 CET, Josselin Morvan <mor...@gm...> a écrit :
>
>
> Hi Alain, hi everyone,
> I'm having trouble removing xml:id attributes with XSLTForms.
> I can insert xml:id attributes, but I cannot delete them using xf:delete.
> As you can see in the attached example, other attributes are removed correctly, but xml:id attributes are not. Is there something I'm missing?
> I'm using XSLTForms 1.7, with Firefox and Chrome.
> Many thanks for you help,
> Josselin
>
>
>
>
> ------------------------------
>
> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Josselin M. <mor...@gm...> - 2025-11-27 20:02:26
|
Hi Alain, hi everyone, I'm having trouble removing |xml:id| attributes with XSLTForms. I can insert |xml:id| attributes, but I cannot delete them using |xf:delete|. As you can see in the attached example, other attributes are removed correctly, but |xml:id| attributes are not. Is there something I'm missing? I'm using XSLTForms 1.7, with Firefox and Chrome. Many thanks for you help, Josselin | | ------------------------------------------------------------------------ |
|
From: Alessandro <ca...@tu...> - 2025-02-06 12:26:25
|
Dear Alain, many thaks for your answer (by the way, if I remember well, I was the one, some years ago, who sent you the Italian config file ;-)) and sorry for the waste of time I've caused to you (see below). As a matter of fact the problem consisted simply in my misunderstanding concerning the right settings of the browser (both Firefox and LibbreWolf). As you can see from the attached screenshot, there are three level for the language settigs and it is not enought to check the last one (as nonetheless would appear to be more logical), because one should also set the "preferred language for displaying pages"... My best regards Alex -- Protetto con Tuta Mail: https://tuta.com/free-email 1 feb 2025, 10:16 da ala...@ag...: > Hi Alex, > > XSLTForms v1.7 includes two mechanisms for internationalization: the legacy one based on config_XXX.xsl files and the new embedded one (Javascript config_data object) for a form to be a standalone HTML file. > > When no language is specified within the form, in legacy mode, XSLTForms gets the navigator language and loads the corresponding config_XXX.xsl file. Using the browser debugger, you should see the HTTP request for it. > > You can force the language using the regular HTML declaration: html/@lang attribute. > > Please find the standard Italian confile file attached. > > If it still does not work for you, I could enhance the new mechanism so it could fix file issues with the legacy one. > > Thank you for your feedback! > > --Alain > >> Le 30/01/2025 15:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Sorry, I've forgotten the screenshot... >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> >> >> 25 gen 2025, 08:18 da ala...@ag...: >> > Hi Alex, >> > >> > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. >> > >> > Could you please post a minimal test form and corresponding screen captures? >> > >> > Thanks! >> > >> > --Alain >> > > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> > > >> > > >> > > Hi all, >> > > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> > > >> > > Many thanks >> > > Alex >> > > >> > > -- >> > > Protetto con Tuta Mail: >> > > https://tuta.com/free-email >> > > _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> |
|
From: Alain C. <ala...@ag...> - 2025-02-01 09:16:40
|
Hi Alex, XSLTForms v1.7 includes two mechanisms for internationalization: the legacy one based on config_XXX.xsl files and the new embedded one (Javascript config_data object) for a form to be a standalone HTML file. When no language is specified within the form, in legacy mode, XSLTForms gets the navigator language and loads the corresponding config_XXX.xsl file. Using the browser debugger, you should see the HTTP request for it. You can force the language using the regular HTML declaration: html/@lang attribute. Please find the standard Italian confile file attached. If it still does not work for you, I could enhance the new mechanism so it could fix file issues with the legacy one. Thank you for your feedback! --Alain > Le 30/01/2025 15:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > Sorry, I've forgotten the screenshot... > > -- > Protetto con Tuta Mail: > https://tuta.com/free-email > > > 25 gen 2025, 08:18 da ala...@ag...: > > Hi Alex, > > > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > > > Could you please post a minimal test form and corresponding screen captures? > > > > Thanks! > > > > --Alain > > > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > > > > > > > Hi all, > > > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... > > > > > > Many thanks > > > Alex > > > > > > -- > > > Protetto con Tuta Mail: > > > https://tuta.com/free-email > > > _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alessandro <ca...@tu...> - 2025-01-30 14:52:05
|
Sorry, I've forgotten the screenshot... -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: > Hi Alex, > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > Could you please post a minimal test form and corresponding screen captures? > > Thanks! > > --Alain > >> Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Hi all, >> even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> >> Many thanks >> Alex >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> |
|
From: Alessandro <ca...@tu...> - 2025-01-30 14:44:30
|
Bonjour Alain, here it is a minimal example of one of the form (displaying the personal data of our workers) and attached you can find the relative screeshot. Mercì beaucoup Alex xquery version "3.1"; import module namespace my_funcs="http://www.my_funcs.net" at "modules/my_app_functions_2.xql"; declare variable $app_collection := '../DATI/XML_DB_files'; declare variable $id_dip := request:get-parameter("id_dip", ""); (: logs into the collection :) let $login := xmldb:login($app_collection, 'admin', 'tom1274') let $dati_personali := doc(concat($app_collection, '/', $my_funcs:my_employees_archive))/dipendenti/dipendente[@id=$id_dip] let $form := <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" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <head> <link rel="stylesheet" type="text/css" href="resources/css/xforms_fonts.css" media="screen,projection"/> <link rel="stylesheet" type="text/css" href="resources/css/schede_dipendenti_2.css" /> <script src="../DATI/XML_DB_files/my_javascripts.js"/> <style type="text/css"> <!--/*--><css><![CDATA[/**/ /*]]>*/<!--/*--></css><!--*/--> </style> <xf:model> <xf:instance id="dati-modificati"> <data xmlns="">{$dati_personali}</data> </xf:instance> <xf:instance id="changes-conf" xmlns=""> <data> <attesa_salvataggio>0</attesa_salvataggio> </data> </xf:instance> <xf:submission ref="instance('dati-modificati')" id="save-dati" method="post" action="query_save_dati_dipendenti.xq?id_dip={$id_dip}"> <xf:action ev:event="xforms-submit-done"> <xf:message level="modal">Dati correttamente aggiornati!</xf:message> </xf:action> <xf:action ev:event="xforms-submit-error"> <xf:message level="modal">Si è verificato un errore in fase di salvataggio!</xf:message> </xf:action> </xf:submission> <!-- BINDS PER CAMPI DATA --> <xf:bind nodeset="instance('dati-modificati')/dipendente/dati/dati_professionali/dta_assunz" type="xs:date"/> <xf:bind nodeset="instance('dati-modificati')/dipendente/dati/dati_personali/d_nascita" type="xs:date" /> </xf:model> </head> <body> <center> <h1>Visualizza e/o modifica dati dipendente</h1> <!-- TABELLA DEI DATI PERSONALI --> <br/> <fieldset id="fieldset-800"> <legend>DATI PERSONALI E PROFESSIONALI</legend> <table border="0" id=""> <tr> <td> <xf:output ref="instance('dati-modificati')/dipendente/@id" class="super-short-input" style="color: red;"> <xf:label><b>ID:</b><br/></xf:label> </xf:output> </td> <td style="width: 20px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/nome" class="long-input"> <xf:label>Nome:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cognome" class="super-long-input"> <xf:label>Cognome:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cf" class="mid-input"> <xf:label>Codice Fiscale:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/d_nascita" class="short-input"> <xf:label>Data nascita:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/l_nascita" class="mid-input"> <xf:label>Luogo nascita:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/tit_studio" class="mid-input"> <xf:label>Tit. studio:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/indirizzo" class="long-input"> <xf:label>Indirizzo:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cap" class="short-input"> <xf:label>CAP:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/citta" class="mid-input"> <xf:label>Città:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/provincia" class="super-short-input"> <xf:label>Provincia:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='1']" class="mid-input"> <xf:label>Telefono 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='2']" class="mid-input"> <xf:label>Telefono 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='3']" class="mid-input"> <xf:label>Telefono 3:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='1']" class="mid-input"> <xf:label>Cellulare 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='2']" class="mid-input"> <xf:label>Cellulare 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='3']" class="mid-input"> <xf:label>Cellulare 3:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/qualifica" class="long-input"> <xf:label>Qualifica:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <!--<xf:input ref="/dipendenti/dipendente[@id='{$id_dip}']/dati/dati_professionali/livello" class="super-short-input">--> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/livello" class="super-short-input"> <xf:label>Livello:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/matr" class="short-input"> <xf:label>Matr:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/dta_assunz" class="short-input" incremental="true" data-bf-params="date:'dd/MM/yyyy'"> <xf:label>Data assunzione:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:select1 ref="instance('dati-modificati')/dipendente/dati/dati_professionali/stato" appearance="minimal" class="select-mid-input"> <xf:label>Stato:<br/></xf:label> <xf:item> <xf:label>Attivo</xf:label> <xf:value>attivo</xf:value> </xf:item> <xf:item> <xf:label>Pensionato</xf:label> <xf:value>pensionato</xf:value> </xf:item> <xf:item> <xf:label>Speciale</xf:label> <xf:value>speciale</xf:value> </xf:item> <xf:item> <xf:label>Cessato</xf:label> <xf:value>cessato</xf:value> </xf:item> </xf:select1> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='1']" class="mid-input-plus"> <xf:label>Mansione/corso 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='2']" class="mid-input-plus"> <xf:label>Mansione/corso 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='3']" class="mid-input-plus"> <xf:label>Mansione/corso 3:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='4']" class="mid-input-plus"> <xf:label>Mansione/corso 4:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='5']" class="mid-input-plus"> <xf:label>Mansione/corso 5:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='6']" class="mid-input-plus"> <xf:label>Mansione/corso 6:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='7']" class="mid-input-plus"> <xf:label>Mansione/corso 7:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='8']" class="mid-input-plus"> <xf:label>Mansione/corso 8:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='9']" class="mid-input-plus"> <xf:label>Mansione/corso 9:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> </fieldset> <br/> <table border="0"> <tr> <td style="height: 40px;"/> <td> <!-- style="padding-top: 15pt;" --> <xf:submit submission="save-dati" > <xf:label class="my_button_2" style="width: 210px;"><b>Salva</b> modifiche ai dati personali</xf:label> </xf:submit> </td> </tr> </table> </center> <br/> <br/> </body> </html> let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'} return ($xslt-pi,$form) -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: Hi Alex, I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. Could you please post a minimal test form and corresponding screen captures? Thanks! --Alain Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : Hi all, even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... Many thanks Alex -- Protetto con Tuta Mail: https://tuta.com/free-email _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: > Hi Alex, > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > Could you please post a minimal test form and corresponding screen captures? > > Thanks! > > --Alain > >> Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Hi all, >> even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> >> Many thanks >> Alex >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> |
|
From: Alain C. <ala...@ag...> - 2025-01-25 08:18:29
|
Hi Alex, I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. Could you please post a minimal test form and corresponding screen captures? Thanks! --Alain > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > Hi all, > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... > > Many thanks > Alex > > -- > Protetto con Tuta Mail: > https://tuta.com/free-email > _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alessandro <ca...@tu...> - 2025-01-21 16:07:32
|
Hi all, even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... Many thanks Alex -- Protetto con Tuta Mail: https://tuta.com/free-email |
|
From: Winona S. <wsa...@gm...> - 2024-02-12 12:25:25
|
Hi Alain, Just checking in on this issue. You said you already had a fix? Any chance I can get a patched xsltforms.js? Thanks for your help, -Winona On Mon, Jan 22, 2024 at 10:07 AM Winona Salesky <wsa...@gm...> wrote: > > Hi Alain, > Thanks for getting back to me and for working on a fix, that will be so helpful. > I did try the latest version of XSLTForms, but it required a lot of rewriting of the forms I already had and I was pressed for time. I hope to have time in the near future to take another look. > -Winona > > > On Sun, Jan 21, 2024 at 3:13 PM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> This issue is due to remaining ids in dependencies which should have been removed when unloading the subform. >> >> I have already a workaround for preventing the exception. I will look for a fix as soon as possible. >> >> I will probably not release some 1.3.1 release but I will send you a patched xsltforms.js instead. >> >> Please give a try to latest XSLTForms release to help me to locate other issues. >> >> --Alain >> >> Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi Alain, >> Thank you so much for all your help with my XForms. I'm having some trouble integrating the TinyMCE example into my much more complex forms set up. I have tried to create a simplified example that still produces the error I am getting. Any chance you could help me debug this? >> Example here: https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b >> >> If I choose the msContents subform from the menu, the TinyMCE text editor works as expected, I can then toggle to my other subform (msIdentifier), but if I then attempt to toggle back to the msContents form again I get the following error (XSLTForms v 1.3): >> >> XSLTForms Exception >> Error dispatching event 'forms-revalidate' : >> TypeError: Cannot read properties of undefined (reading 'length') at new XsltForms_exprContext(../xsltforms.js:4121:43) >> >> >> Toggling between these subforms without the TinyMCE additions work without error, but I'm unsure what exactly is causing the error with the addition of the TinyMCE code. Do you have any suggestions or insights? >> Thank you again for your help, >> -Winona >> >> >> >> >> >> On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <wsa...@gm...> wrote: >> >> Hi Alain, >> That did fix the example. Thank you. I think I have misunderstood the use of the XForms binding. So I will do a little research and see if I can get them working correctly on my more complex version of the form, which has the summary element at many different levels in the TEI record. >> >> -Winona >> >> >> On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> Looking at the simplified example, it appears that the new record does not have the very same structure: the document root is named "TEI" with a child named "data" whilst the pre-loaded document has the "data" element as root. >> >> XForms bindings are context dependant, they are not like XSLT template match attribute values. >> >> Whether subforms are used should not interfere with bindings. >> >> Thank you for your feedback! >> >> --Alain >> >> Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi Alain, >> This sort of works. Here is an example of multiple text editors working: https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 >> >> However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors. >> Here is a simplified example: https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 >> >> Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not. >> Thanks! >> -Winona >> >> >> On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> Sorry for the delay. >> >> Please have a look at the tinymce.xml sample (https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). >> >> Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample: >> <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> >> >> In next release, XSLTForms will also check "tinymce.majorVersion + '.' + tinymce.minorVersion", as suggested by ChatGPT ;-) >> >> After upgrading the repeat test case accordingly, it works as expected for me! >> >> Thank you for your feedback! >> >> --Alain >> >> Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi All, >> I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example: >> http://www.agencexml.com/xsltforms/tinymce.xml >> >> But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue. >> >> Thanks! >> -Winona >> >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Winona S. <wsa...@gm...> - 2024-02-02 17:41:28
|
Great news, thanks for the update and the example.
-Winona
On Fri, Feb 2, 2024 at 10:56 AM Steven Pemberton <ste...@cw...>
wrote:
> Winona,
>
> We have discussed this in the WG, and resolved to add @dir to the Common
> set of attributes.
>
> In the meantime, as Alain has already pointed out, you can legally use
> html:dir anywhere in XForms, as foreign namespaced attributes are allowable
> everywhere, and furthermore, you can use CSS properties for the same
> effect. For instance:
>
> *[class="ltr"] { unicode-bidi: embed; direction: ltr}
> *[class="rtl"] { unicode-bidi: embed; direction: rtl}
> *[class="lro"] { unicode-bidi: bidi-override; direction: ltr}
> *[class="rlo"] { unicode-bidi: bidi-override; direction: rtl}
>
> I show a quick example at https://cwi.nl/~steven/forms/tests/bidi.xhtml
>
> Best wishes,
>
> Steven
>
> On Thursday 07 December 2023 17:11:16 (+01:00), Winona Salesky wrote:
>
> Hi All,
> I need to support both rtl and ltr text input in my forms. Reading up on
> this online, it sounds like the best way to do this is to include the
> following attribute on the input/textarea elements: dir="auto"
>
> What do you think the best way to get this working in XSLTForms is? Edit
> the XSLTForms javascript? Write my own Javascript to amend the output?
> Something else?
>
> Thanks for any thoughts or suggestions.
> -Winona
>
>
|
|
From: Steven P. <ste...@cw...> - 2024-02-02 16:14:09
|
Winona,
We have discussed this in the WG, and resolved to add @dir to the Common
set of attributes.
In the meantime, as Alain has already pointed out, you can legally use
html:dir anywhere in XForms, as foreign namespaced attributes are allowable
everywhere, and furthermore, you can use CSS properties for the same
effect. For instance:
*[class="ltr"] { unicode-bidi: embed; direction: ltr}
*[class="rtl"] { unicode-bidi: embed; direction: rtl}
*[class="lro"] { unicode-bidi: bidi-override; direction: ltr}
*[class="rlo"] { unicode-bidi: bidi-override; direction: rtl}
I show a quick example at https://cwi.nl/~steven/forms/tests/bidi.xhtml
Best wishes,
Steven
On Thursday 07 December 2023 17:11:16 (+01:00), Winona Salesky wrote:
Hi All,
I need to support both rtl and ltr text input in my forms. Reading up on
this online, it sounds like the best way to do this is to include the
following attribute on the input/textarea elements: dir="auto"
What do you think the best way to get this working in XSLTForms is? Edit
the XSLTForms javascript? Write my own Javascript to amend the output?
Something else?
Thanks for any thoughts or suggestions.
-Winona |
|
From: Winona S. <wsa...@gm...> - 2024-01-24 19:37:36
|
Hi All, I'm running XSLTForms in eXist-db and experiencing some caching issues that prevent my forms from reloading, for example: I edit one record. Save it, and open a new record (same form) but the new record does not show up, I get a cached version of the form. Anyone else running into this and have a good solution? Thanks for the help, -Winona |
|
From: Winona S. <wsa...@gm...> - 2024-01-22 15:07:40
|
Hi Alain, Thanks for getting back to me and for working on a fix, that will be so helpful. I did try the latest version of XSLTForms, but it required a lot of rewriting of the forms I already had and I was pressed for time. I hope to have time in the near future to take another look. -Winona On Sun, Jan 21, 2024 at 3:13 PM Alain Couthures < ala...@ag...> wrote: > Hi Winona, > > This issue is due to remaining ids in dependencies which should have been > removed when unloading the subform. > > I have already a workaround for preventing the exception. I will look for > a fix as soon as possible. > > I will probably not release some 1.3.1 release but I will send you a > patched xsltforms.js instead. > > Please give a try to latest XSLTForms release to help me to locate other > issues. > > --Alain > > Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi Alain, > Thank you so much for all your help with my XForms. I'm having some > trouble integrating the TinyMCE example into my much more complex forms set > up. I have tried to create a simplified example that still produces the > error I am getting. Any chance you could help me debug this? > Example here: > https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b > > If I choose the msContents subform from the menu, the TinyMCE text editor > works as expected, I can then toggle to my other subform (msIdentifier), > but if I then attempt to toggle back to the msContents form again I get the > following error (XSLTForms v 1.3): > > XSLTForms Exception > Error dispatching event 'forms-revalidate' : > TypeError: Cannot read properties of undefined (reading 'length') at new > XsltForms_exprContext(../xsltforms.js:4121:43) > > > Toggling between these subforms without the TinyMCE additions work without > error, but I'm unsure what exactly is causing the error with the addition > of the TinyMCE code. Do you have any suggestions or insights? > Thank you again for your help, > -Winona > > > > > > On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <wsa...@gm...> wrote: > > Hi Alain, > That did fix the example. Thank you. I think I have misunderstood the use > of the XForms binding. So I will do a little research and see if I can get > them working correctly on my more complex version of the form, which has > the summary element at many different levels in the TEI record. > > -Winona > > > On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures < > ala...@ag...> wrote: > > Hi Winona, > > Looking at the simplified example, it appears that the new record does not > have the very same structure: the document root is named "TEI" with a child > named "data" whilst the pre-loaded document has the "data" element as root. > > XForms bindings are context dependant, they are not like XSLT template > match attribute values. > > Whether subforms are used should not interfere with bindings. > > Thank you for your feedback! > > --Alain > > Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi Alain, > This sort of works. Here is an example of multiple text editors working: > https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 > > However, when I try to use this in my actual forms I run into issue. I > think it is because my data is loaded after the form is loaded. The user is > presented with a main form that allows them to search for records or load a > 'template' record into the form. If the data is pre-loaded, the tinyMCE > editor works, once I select and load a new record, the textarea are > displayed a regular textareas, not as tinyMCE editors. > Here is a simplified example: > https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 > > Any thoughts on how to solve this issue? Also, many of my textareas that I > want editable will be in subforms. Not sure if that adds another layer of > complication or not. > Thanks! > -Winona > > > On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures < > ala...@ag...> wrote: > > Hi Winona, > > Sorry for the delay. > > Please have a look at the tinymce.xml sample ( > https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). > > > Because of compatibility issues between tinymce versions, it is required > to add data-uri and data-version attributes to allow XSLTForms to properly > manage the rich text editors. In the sample: > <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" > data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> > > In next release, XSLTForms will also check "tinymce.majorVersion + '.' + > tinymce.minorVersion", as suggested by ChatGPT ;-) > > After upgrading the repeat test case accordingly, it works as expected for > me! > > Thank you for your feedback! > > --Alain > > Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi All, > I'm looking into adding a rich text editor to my textarea's. I was trying > to experiment with this example: > http://www.agencexml.com/xsltforms/tinymce.xml > > But have had some trouble getting it working. My use case would include > multiple textarea's almost all of them appearing in a nested repeat > structure. I found this on the list ( > https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) > which suggests repeats could be a problem. Has this been solved? Has anyone > integrated a text editor into their XForms? I can mock up a > simplified example of what I am trying to do if that would be useful, but > I'm mostly looking for examples for how someone else may have solved this > issue. > > Thanks! > -Winona > > _______________________________________________ Xsltforms-support mailing > list Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alain C. <ala...@ag...> - 2024-01-21 20:14:14
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
</div>
<div class="default-style">
This issue is due to remaining ids in dependencies which should have been removed when unloading the subform.
</div>
<div class="default-style">
</div>
<div class="default-style">
I have already a workaround for preventing the exception. I will look for a fix as soon as possible.
</div>
<div class="default-style">
</div>
<div class="default-style">
I will probably not release some 1.3.1 release but I will send you a patched xsltforms.js instead.
</div>
<div class="default-style">
</div>
<div class="default-style">
Please give a try to latest XSLTForms release to help me to locate other issues.
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<div>
Thank you so much for all your help with my XForms. I'm having some trouble integrating the TinyMCE example into my much more complex forms set up. I have tried to create a simplified example that still produces the error I am getting. Any chance you could help me debug this?
<br>Example here: <a href="https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b">https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b</a>
<br>
<br>If I choose the msContents subform from the menu, the TinyMCE text editor works as expected, I can then toggle to my other subform (msIdentifier), but if I then attempt to toggle back to the msContents form again I get the following error (XSLTForms v 1.3):
<br>
<br><span style="font-family: monospace;">XSLTForms Exception<br>Error dispatching event 'forms-revalidate' :<br>TypeError: Cannot read properties of undefined (reading 'length') at new XsltForms_exprContext(../xsltforms.js:4121:43)<br><br></span>
<br>Toggling between these subforms without the TinyMCE additions work without error, but I'm unsure what exactly is causing the error with the addition of the TinyMCE code. Do you have any suggestions or insights?
<br>Thank you again for your help,
</div>
<div>
-Winona
<br>
<br>
<br>
<br>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <<a href="mailto:wsa...@gm...">wsa...@gm...</a>> wrote:
</div>
<blockquote>
<div dir="ltr">
Hi Alain,
<div>
That did fix the example. Thank you. I think I have misunderstood the use of the XForms binding. So I will do a little research and see if I can get them working correctly on my more complex version of the form, which has the summary element at many different levels in the TEI record.
</div>
<div>
</div>
<div>
-Winona
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures <<a href="mailto:ala...@ag..." target="_blank" rel="noopener">ala...@ag...</a>> wrote:
</div>
<blockquote>
<u></u>
<div>
<div>
Hi Winona,
</div>
<div>
</div>
<div>
Looking at the simplified example, it appears that the new record does not have the very same structure: the document root is named "TEI" with a child named "data" whilst the pre-loaded document has the "data" element as root.
</div>
<div>
</div>
<div>
XForms bindings are context dependant, they are not like XSLT template match attribute values.
</div>
<div>
</div>
<div>
Whether subforms are used should not interfere with bindings.
</div>
<div>
</div>
<div>
Thank you for your feedback!
</div>
<div>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 03/01/2024 00:54 CET, Winona Salesky <<a href="mailto:wsa...@gm..." target="_blank" rel="noopener">wsa...@gm...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<div>
This sort of works. Here is an example of multiple text editors working: <a href="https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35" target="_blank" rel="noopener">https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35</a>
</div>
<div>
</div>
<div>
However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors.
</div>
<div>
Here is a simplified example: <a href="https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2" target="_blank" rel="noopener">https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2</a>
<br>
<br>Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not.
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures <<a href="mailto:ala...@ag..." target="_blank" rel="noopener">ala...@ag...</a>> wrote:
</div>
<blockquote>
<u></u>
<div>
<div>
Hi Winona,
</div>
<div>
<div>
</div>
<div>
Sorry for the delay.
</div>
<div>
</div>
</div>
<div>
Please have a look at the tinymce.xml sample (<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)" target="_blank" rel="noopener">https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)</a>.
</div>
<div>
</div>
<div>
Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample:
<br><script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="<a href="http://www.tinymce.com" target="_blank" rel="noopener">http://www.tinymce.com</a>" data-version="4.5.3">/* */</script>
</div>
<div>
</div>
<div>
In next release, XSLTForms will also check "tinymce.majorVersion + '.' + tinymce.minorVersion", as suggested by ChatGPT ;-)
</div>
<div>
</div>
<div>
After upgrading the repeat test case accordingly, it works as expected for me!
</div>
<div>
</div>
<div>
Thank you for your feedback!
</div>
<div>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 17/12/2023 19:30 CET, Winona Salesky <<a href="mailto:wsa...@gm..." target="_blank" rel="noopener">wsa...@gm...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi All,
<br>
<div>
I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example:
</div>
<div>
<a href="http://www.agencexml.com/xsltforms/tinymce.xml" target="_blank" rel="noopener">http://www.agencexml.com/xsltforms/tinymce.xml</a>
</div>
<div>
</div>
<div>
But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (<a href="https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903" target="_blank" rel="noopener">https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903</a>) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue.
</div>
<div>
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list <a href="mailto:Xsl...@li..." target="_blank" rel="noopener">Xsl...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>
|