the fr:number component no longer updates the data in the xml instance

45 views
Skip to first unread message

julien bittard

unread,
Nov 18, 2022, 6:22:45 AM11/18/22
to Orbeon Forms
We have moved from version 4.4 to 2020, and we have a problem with the use of fr:number in our XFORMS forms.
I reproduced this problem on the default orbeon 2021 war by modifying the "expresso-order" example to handle the quantity with a fr-number.
I attach my modification to the email.
The problem is that the value entered in the field is not saved in the xml instance, which makes it, among other things, never valid.
Another problem, the icon showing that the field is invalid is displayed, but the associated tooltip does not appear.


To be able to use the fr:number component, I added the namespace xmlns:fr="http://orbeon.org/oxf/xml/form-runner", and the attribute xxf:function-library="org. orbeon.oxf.fr.library.FormRunnerFunctionLibrary" on the <xf:model> tag.
There is no error in the logs (which are debug level and oxf.run-mode with the value "dev").

It is blocking in our deployment of this version of Orbeon, do you have an idea of ​​the source of the problem?

Thank You

Julien
expressoorder-frnumber.xhtml

Alessandro Vernet

unread,
Nov 21, 2022, 1:44:04 AM11/21/22
to orb...@googlegroups.com
Hi Julien,

Got it, I can reproduce this, and for now created issue #5533 (see link below). Maybe unrelated, is there any particular reason you're looking into updating to 2020, and not 2021?

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/a94ed089-e7c7-4e75-8541-6968e901a19en%40googlegroups.com.

Bittard, Julien

unread,
Nov 21, 2022, 4:07:44 AM11/21/22
to orb...@googlegroups.com

Hi Alessandro,

 

Thank You for the issue.

We stopped at the 2020 because we are still using the xupdate processor. And it still works in 2020, manually including the .jar file, but no longer in 2021.

I know it's not very pretty, but modifying our code to stop using it is too impactful for us. We are considering recovering the sources of the xupdate component to keep it compatible with new versions of Orbeon.

 

Thank You

 

Julien

 

 

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : lundi 21 novembre 2022 07:44
À : orb...@googlegroups.com
Objet : Re: [orbeon] the fr:number component no longer updates the data in the xml instance

 

EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

 

Alessandro Vernet

unread,
Nov 21, 2022, 7:12:52 PM11/21/22
to orb...@googlegroups.com
Hi Julien,

Got it about 2020 and the XUpdate processor. And yes, I think it shouldn't be too hard to take the code of the XUpdate processor, build it yourself, and run it on the latest release.

-Alex

Bittard, Julien

unread,
Nov 22, 2022, 3:13:20 AM11/22/22
to orb...@googlegroups.com

Hi Alessandro,

 

Thank you for confirmation.

Regarding the problem with "fr:number", do you have any idea of a fix?

 

Thank You

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : mardi 22 novembre 2022 01:13

Alessandro Vernet

unread,
Nov 22, 2022, 5:16:35 PM11/22/22
to orb...@googlegroups.com
Hi Julien,

One problem is with the calls to `fr:component-param-value()` from `xxbl:format`, and elsewhere, which are not available in plain XForms. Instead, we should call `xxf:component-param-value()`. Erik is working on a mechanism to allow this.


Alessandro Vernet

unread,
Dec 15, 2022, 11:43:22 AM12/15/22
to orb...@googlegroups.com
Hi Julien,

As a quick update on this, we have already taken some steps to support `fr:number` and `fr:date` in plain XForms, but will not manage to complete this for the 2022.1 release; so this has been moved for 2022.1.1.

-Alex

Bittard, Julien

unread,
Dec 15, 2022, 12:12:32 PM12/15/22
to orb...@googlegroups.com

Hi Alex,

 

Thanks for the news.

If I understood correctly on the ticket, the correction cannot be carried over to 2021?

and what is the planned date for 2022.1.1?

 

Thank You

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : jeudi 15 décembre 2022 17:43

Alessandro Vernet

unread,
Dec 15, 2022, 7:27:31 PM12/15/22
to orb...@googlegroups.com
Hi Julien,

Whether this might be backported to a 2021.1.x release, will be influenced by technical difficulty and risk, as well as demand from customers. I don't think that we have enough information to make a determination yet.

I would expect the first 2022.1.1 point release in the first couple of months of the year. At least, that has been the tendency during the last few years ;). https://doc.orbeon.com/release-history

-Alex

Bittard, Julien

unread,
Jan 5, 2023, 1:44:24 PM1/5/23
to orb...@googlegroups.com

Hi Alex,

 

I saw that the problem was progressing but that there were still corrections to be made.

In our application we do not use "Form Runner" but only "plain Xforms", is there not a quick and temporary correction that we could apply to our version of orbeon while waiting for the final fix?

For example, modifying the "number.xbl" file so that it just works in "plain xforms"?

I tried to deduce this by looking at the corrections you have already uploaded, but I can't figure out what exactly is missing.

 

Because it becomes blocking on our side and we would need this quick correction.

 

Thanks

 

Julien

 

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : vendredi 16 décembre 2022 01:27

Alessandro Vernet

unread,
Jan 11, 2023, 1:27:14 AM1/11/23
to orb...@googlegroups.com
Hi Julien,

As a local workaround, you could try replacing the calls to `fr:component-param-value()` by calls to `xxf:component-param-value()`. You'll let me know if this helps.


Bittard, Julien

unread,
Jan 11, 2023, 5:19:50 AM1/11/23
to orb...@googlegroups.com

Hi Alex,

 

I tried, but it doesn't change anything: the entered value is not stored in the instance.

The other symptom is that the alert's tooltip also does not show when hovering the mouse over it.

And finally, despite the activation of all the debug logs, I have no error message, and therefore I cannot see what is causing the problem.

Do you have another quick fix?

 

Thank You.

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : mercredi 11 janvier 2023 07:27

Alessandro Vernet

unread,
Jan 18, 2023, 5:56:10 PM1/18/23
to orb...@googlegroups.com
Hi Julien,

Try the following example, which works for me with both 2022.1 and 2021.1.6. The component shows ok, and the value in the data updates as you change the value. No change to the `number.xbl` needed. Are you seeing any issue?

-Alex

view.xhtml

Bittard, Julien

unread,
Jan 19, 2023, 4:37:41 AM1/19/23
to orb...@googlegroups.com
Hi Alex

I confirm that it works in 2021, but not in 2020. Another question is that these modifications can be applied in a general way to the application?  in order to avoid modifying each page?

Thank you very much Alex

Cordialement 
Julien Bittard 


De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Date : mercredi 18 janv. 2023 à 11:57 PM

Alessandro Vernet

unread,
Jan 19, 2023, 5:04:34 PM1/19/23
to orb...@googlegroups.com
Hi Julien,

Good. One way to apply those changes to all the forms would be to use XSLT, if you already have a stylesheet that runs on your forms. In fact, this is what Form Runner does.

-Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/c9a18bf4182b4c45b231af19cfcb6dae%40cgi.com.

Bittard, Julien

unread,
Feb 8, 2023, 5:54:00 AM2/8/23
to orb...@googlegroups.com

Hi Alex,

 

I succeeded in applying the fix on my pages with a <fr:number> field.

On the other hand, the consequence is that all "xf:alert" are then displayed as in the Form Builder, i.e. with the error message under the field concerned, and no longer via a red exclamation point in end of field with the error message in "tooltip".

 

Will the final correction of the problem also have this consequence? or will we find the classic "plain xforms" display of the alert message?

 

Because many of our pages do not "support" this new display well, it is superimposed for example with the other input fields.

So that would require a lot of work on our css styles.

 

Thank You.

 

Julien

 

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : jeudi 19 janvier 2023 23:04

Alessandro Vernet

unread,
Feb 9, 2023, 1:45:04 AM2/9/23
to orb...@googlegroups.com
Hi Julien,

Would just not including the Form Runner CSS work for you, by not adding that CSS in the `xxf:assets.baseline.updates`, i.e. keep the value of this property to the following?

    xxf:assets.baseline.updates="
        -/ops/javascript/scalajs/orbeon-xforms-web.js
        +/apps/fr/resources/scalajs/orbeon-form-runner-web.js
    "

-Alex

Bittard, Julien

unread,
Feb 9, 2023, 3:10:56 AM2/9/23
to orb...@googlegroups.com

Hi,

 

I tested without the CSS files, and indeed I found the "xf:alert" formatting for all the fields.

On the other hand, the "tooltip" is missing on the <fr:number> field.

The alert message is well displayed in the <fr:error-summary> , but it does not display when hovering over the exclamation mark.

 

Attached are screenshots showing a test without the fix, with the fix, and with the fix but without the css included.

 

Thank You.

 

Julien

 

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : jeudi 9 février 2023 07:45

with fix frnumber.png
without fix frnumber.png
with fix frnumber without css.png

Alessandro Vernet

unread,
Feb 14, 2023, 2:40:47 PM2/14/23
to orb...@googlegroups.com
Hi Julien,

You are saying that without the Form Runner CSS, then the `<xf:hint>` doesn't show any more as a tool tip, but instead shows below the field. If so, keeping the Form Runner CSS, you can switch to the "tooltip behavior" by adding `xxf:hint.appearance="tooltip"` on the model. I've attached an updated example that illustrates this.

Screenshot 2023-02-14 at 11.39.44 AM.png

-Alex

view.xhtml

julien bittard

unread,
Feb 15, 2023, 1:23:03 PM2/15/23
to Orbeon Forms
Hi Alex,

I think there is a misunderstanding, because I was not clear in my screenshots: it's not the <xf:hint> , but the <xf:alert> that I would like to have in "tooltip".
In the screenshots provided, the messages "alarme", or "Vous devez saisir votre login" are indicated in the <xf:alert> of each field. The first is a <fr:number> field, the second and third are <xf:input> fields.

I tried what you suggested, but it didn't work.
The ideal for us is to have the correction without the Form Runner CSS.
But then, the alert message is no longer displayed at all at the level of the <fr:number> field, whether in "tooltip" or other. It is just present in the <error-summary>: it is this point that is missing for a perfect correction :)
Attached is an example with an <xf:alert> on the <fr:number>.

Thank You

Julien
view_frnumberalert.xhtml

Alessandro Vernet

unread,
Feb 16, 2023, 7:42:37 PM2/16/23
to orb...@googlegroups.com
Hi Julien,

On Wed, Feb 15, 2023 at 10:23 AM julien bittard <ricet...@gmail.com> wrote:
I think there is a misunderstanding, because I was not clear in my screenshots: it's not the <xf:hint> , but the <xf:alert> that I would like to have in "tooltip".
In the screenshots provided, the messages "alarme", or "Vous devez saisir votre login" are indicated in the <xf:alert> of each field. The first is a <fr:number> field, the second and third are <xf:input> fields.

 The `<xf:alert>` specifies a message shown when a field is invalid. In the example you've attached to your message, if I add a `<xf:bind ref="." constraint="false()"/>` to make the field always invalid (modified source attached), then I get a red exclamation mark icon next to the field:

Screenshot 2023-02-16 at 4.38.29 PM.png
I think that in the past, a tooltip with the alert message was showing when you were hovering with your mouse pointer over that icon. Is this what you are referring to?

-Alex
view.xhtml

julien bittard

unread,
Feb 17, 2023, 2:23:36 AM2/17/23
to orb...@googlegroups.com
Hi

Yes it’s exactly what i mean. 
But now , on fr:number field, There is’nt anymore message showing.

Thank you

Julien
De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : vendredi, février 17, 2023 1:42 AM

À : orb...@googlegroups.com <orb...@googlegroups.com>
Objet : Re: [orbeon] the fr:number component no longer updates the data in the xml instance
 
--
You received this message because you are subscribed to a topic in the Google Groups "Orbeon Forms" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orbeon/Ex880YIuZxA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orbeon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/CANrzKkm9fjm9oMvsqe49PCrgfhBRX-HUYn_hfN%2BDdtSpT3Yu8Q%40mail.gmail.com.

Alessandro Vernet

unread,
Feb 20, 2023, 1:15:21 AM2/20/23
to orb...@googlegroups.com
Hi Julien,

Got it, however I am not seeing the tooltip on mouseover even for a plain text input, e.g. with the attached example. Am I missing anything? If not, when was the last time this worked for you, i.e. with what version of Orbeon Forms?

-Alex

You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/DBBP189MB146712753D3C18B753C0ED65A9A19%40DBBP189MB1467.EURP189.PROD.OUTLOOK.COM.
view.xhtml

Bittard, Julien

unread,
Feb 20, 2023, 11:32:09 AM2/20/23
to orb...@googlegroups.com

Hi Alex,

 

I am using the 2021 version of ORBEON to reproduce the problem.

Try with the example I sent at the start, based on the "expresso-order.xhtml"

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : lundi 20 février 2023 07:15
À : orb...@googlegroups.com


Objet : Re: [orbeon] the fr:number component no longer updates the data in the xml instance

 

EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe.


EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

 

Hi Julien,

expressoorder-frnumber.xhtml

Alessandro Vernet

unread,
Feb 26, 2023, 3:38:12 AM2/26/23
to orb...@googlegroups.com
Hi Julien,

Sorry, my last message wasn't clear: I was asking on which version of Orbeon Forms you've last seen this working, i.e. which version was correctly showing a tooltip when hovering the alert icon, even for a plain text field? (I'm asking because the code seems incorrect to me, but hasn't changed in a long, long time.)

-Alex

julien bittard

unread,
Feb 26, 2023, 7:55:53 AM2/26/23
to orb...@googlegroups.com
Hi alex

Ok , it’s on orbeon 4.4.1 …  😅

Envoyé à partir de Outlook pour iOS
De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : Sunday, February 26, 2023 9:37:53 AM

Alessandro Vernet

unread,
Mar 1, 2023, 2:45:16 AM3/1/23
to orb...@googlegroups.com
Hi Julien,

Got it. And I see what is happening. Actually this regressed quite recently, while fixing #3669. The thing is that the change (in `_findParentXFormsControl`) made sense, and it is the caller code (in `mouseover`) that was making an incorrect assumption. I am looking into it!

-Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/AS8P189MB1463543BEA4CFD1ACE81109CA9AE9%40AS8P189MB1463.EURP189.PROD.OUTLOOK.COM.

Bittard, Julien

unread,
Mar 1, 2023, 3:45:42 AM3/1/23
to orb...@googlegroups.com

Hi Alex,

 

Good news. But, the issue you indicate seems to be fixed in version 2022.1 only (https://github.com/orbeon/orbeon-forms/issues/3669) so I don't understand how it can be a regression on previous versions.

 

Thank You.

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : mercredi 1 mars 2023 08:45

Alessandro Vernet

unread,
Mar 2, 2023, 6:46:31 PM3/2/23
to orb...@googlegroups.com
Hi Julien,

The fix also went into 2021.1.2, so at this point this is most likely broken in 2021.1.x and 2022.1.x, and still working on 2020.1.x and earlier. The code I was looking at hasn't changed in a while, but the issue is caused by a modification we've made to a function called by that code, hence the confusion ;). I'll make sure to let you know when we have a fix for this.

-Alex

Bittard, Julien

unread,
Mar 3, 2023, 9:12:09 AM3/3/23
to orb...@googlegroups.com

Hi Alex,

 

Thank you for the explanations. I am indeed waiting for your return, I hope positive, because this problem blocks the release of the new version of our application.

 

Thank You .

 

Julien

 

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : vendredi 3 mars 2023 00:46

Alessandro Vernet

unread,
Mar 8, 2023, 4:04:00 PM3/8/23
to orb...@googlegroups.com
Hi Julien,

Here we go: the issues with the tooltips that I could see (#5712) are now fixed, and this will be in 2022.1.3. Let me know if having a 2022.1.2+ test build would help.


Bittard, Julien

unread,
Mar 9, 2023, 2:53:03 AM3/9/23
to orb...@googlegroups.com

Hi Alex.

Good news ! Thank’s for that.

For the moment we are in version 2020 of ORBEON, and we plan to switch to 2021 to unblock the problem.

Is it possible to postpone the correction of https://github.com/orbeon/orbeon-forms/issues/5712 to 2021?

I can take care of it locally and modify the xforms.js file by applying your correction, and indicating in the oxf.xforms.assets.baseline property not to take the xforms.js file in "min=true"?

 

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : mercredi 8 mars 2023 22:04

Alessandro Vernet

unread,
Mar 9, 2023, 5:25:53 PM3/9/23
to orb...@googlegroups.com
Hi Julien,

The fix for the tooltips will go in 2022.1.3. I imagine that we could also put it on 2021.1.8; but are you using Orbeon Forms PE? If not, I imagine it doesn't make much of a difference to you whether we also back ports this to 2021.1.8, or am I maybe misreading your question?

-Alex

julien bittard

unread,
Mar 10, 2023, 1:00:03 AM3/10/23
to orb...@googlegroups.com
Hi Alex 

my goal is to provide a fix as soon as possible.  we use ORBEON CE.  My proposal was to apply the tooltip correction myself to go faster because I don't know when 2021.1.8 will be available

Thank’s

Julien

Envoyé à partir de Outlook pour iOS
De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>
Envoyé : Thursday, March 9, 2023 11:25:35 PM

Alessandro Vernet

unread,
Mar 10, 2023, 11:52:20 AM3/10/23
to orb...@googlegroups.com
Hi Julien,

When we backport fixes, they only go on the PE branches, so 2021.1.8 would be a PE release, which wouldn't be of much use to you if you are using the CE. If everything is working out for you with the number field on the 2021.1 CE you are using, and the only problem is with the tooltips, then you can try to apply the change done to fix that tooltips issue on that version.

The changes are all in two functions defined in the single file (the plain old `xforms.js`), and I suspect that code hasn't changed much since 2021.1, so that might be quite doable.

https://github.com/orbeon/orbeon-forms/commit/b0a8e63c97f1dac05f8eb5cecb7262b7b3961bc6

-Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/orbeon/DBBP189MB146778A1F512EB76872CB0D1A9BA9%40DBBP189MB1467.EURP189.PROD.OUTLOOK.COM.

Julien Bittard

unread,
Mar 18, 2023, 12:45:46 PM3/18/23
to orb...@googlegroups.com

Hi Alex,

 

Thanks for the explanation. I applied the patch on the xforms.js file of the 2021 version and it works perfectly. We will be able to offer this to our customers.

 

Thank You

 

Julien

 

De : 'Alessandro Vernet' via Orbeon Forms <orb...@googlegroups.com>

Envoyé : vendredi 10 mars 2023 17:52

image001.png

Alessandro Vernet

unread,
Mar 20, 2023, 5:19:40 PM3/20/23
to orb...@googlegroups.com
Perfect Julien, I am glad that this worked out.

-Alex

Reply all
Reply to author
Forward
0 new messages