Using variable of currency component in template makes the decimals (,00) disappear from the component

[SilviaAmAm]

Product versie / Product version

2.0.0

Omschrijf het probleem / Describe the bug

Taiga DH issue 311, user story 314

Referencing a currency component in a content component, causes the formatting to change in the currency component.

Stappen om te reproduceren / Steps to reproduce

Create a new form with:

• A currency component (with key currency)
• A content component with the content: Test: {{ currency }}

Now try to fill in the form:

• When the currency component is empty, the content component shows Test: None
• Fill in 123 in the currency component. On blur, the currency is formatted to 123,00
• When the content component changes to Test: 123, the ,00 disappears from the currency component.

Verwacht gedrag / Expected behavior

The formatting of the currency component should remain constant.

Screen resolution

No response

Device

No response

OS

No response

Browser

No response

[SilviaAmAm]

What happens:

• The user fills in the value 123
• On blur, the value gets formatted (addZerosAndFormatValue). This takes the value 123 and formats it to € 123,00
• The value 123 is sent to the backend.
• The response from the backend contains no changes to the submission step data, but the configuration has changed.
• The form is reloaded, but because there is no blur event, the decimal is not re-added.
• The currency symbol remains because its in the mask

[SilviaAmAm]

Discussed:

• Bandaid solution: for now make the data that comes back from the backend have the decimals. => This didn't workout (JSON only has Number field, so we cannot send a float formatted with 2 decimal values. Sending strings has the problem of the locale). => Try checking if an onChange event was programmatic, if yes, perform onBlur code.
• Deal with this properly in https://github.com/open-formulieren/open-forms/issues/2324

[SilviaAmAm]

Note: Den Haag issue 310 / user story 313:

Create a form with:

• a required text field
• a content component that uses the value of the text field

Fill in the form:

• Fill the text field with a value test => The content component shows this new value
• Delete the value of the text field => An error appears to say that the field is required
• When the configuration is reloaded, the error disappears

[SilviaAmAm]

Note2: Den Haag issue 309 / user story 312

Create a form with:

• Any field
• A content component using the value of the field above
• A repeating group with any field inside

Fill in the form:

• Add an iteration of the repeating group (don't fill anything in yet)
• Fill in a value for the first field => The iteration automatically closes itself when the configuration reloads

[joeribekker]

Seems like this was already reported in #1341

[joeribekker]

Decided to set it to low because, although annoying, technically there is nothing wrong.

[SilviaAmAm]

Note 3: Den Haag issue 457

Reloading of the form resets the focus for keyboard navigation

Create a form with:

• A textfield
• A radio field
• A hidden text field
• A backend logic rule saying: if the first text field has value 'test', make the second textfield visible

Now fill in the form:

• Fill in the first text field with the value 'test'
• With the tab key navigate to the radio button
• Observe that when the configuration changes, the focus on the radio button disappears

[joeribekker]

@Silvia will make a meta ticket that links all the related/commented issues together to keep this issue on its own (decimals).

[SilviaAmAm]

Meta ticket: https://github.com/open-formulieren/open-forms/issues/2934