Wrong decimal point separator

Oct 13, 2025 by talynt.org 94 views

Introduction

In this article, we will discuss a bug that occurs when using a decimal type input field in a web application. The bug is related to the decimal point separator, where the field shows the wrong separator, specifically the comma (,) instead of the period (.) as expected. This issue is observed in a financial application that requires formatting numbers in the United States style (e.g., 300.44).

Describe the Bug

The bug is described as follows:

Decimal type input field: The input field is created with the type 'Decimal', and the precision and scale are set.
Wrong decimal point separator: When editing an entry that has been saved with the correct decimal point separator (.), the field shows the wrong separator, which is the comma (,).
Correct value in database: The value is saved correctly in the database with the correct decimal point separator (.), but the field shows the wrong separator when editing the entry.
API returns correct value: The API returns the correct value with the correct decimal point separator (.), but the field shows the wrong separator when editing the entry.
Overview lists show correct value: Overview lists show the correct value with the correct decimal point separator (.), but the field shows the wrong separator when editing the entry.

Additional Information

MySQL as database: The database used is MySQL, which supports the Decimal data type.
Belgium locale: The system's locale is set to Belgium (nl-BE), and the OS version is set to English.
Number formatting: Locally, numbers are formatted like 300,44 instead of 300.44.
Financial application: The application requires formatting numbers in the United States style (e.g., 300.44).
Browser locale and headers: The browser locale and headers are set to en-US.
Admin profile and project settings: The admin profile and project settings are explicitly set to "English (United States)".

To Reproduce

To reproduce the bug, follow these steps:

Set computer date and number formatting: Set the computer date and number formatting to Belgium.
Set system language default: Set the system language default to English (United States).
Create a decimal field: Create a decimal field.
Enter a number en-us formatted: Enter a number in the United States style (e.g., 300.44).
Save the entry: Save the entry.
Edit the entry: Edit the entry.
Value in the field: The value in the field should show 300,44.

Directus Version

The Directus version used is v11.5.1.

Hosting Strategy

The hosting strategy used is Self-Hosted (Docker Image).

Database

The database used is MySQL v8.

Conclusion

In conclusion, the bug occurs due to the incorrect decimal point separator being displayed in the decimal type input field. The field shows the comma (,) instead of the period (.) as expected. This issue is observed in a financial application that requires formatting numbers in the United States style (e.g., 300.44). The bug is not related to the profile or project setting locale, and it occurs even when the browser locale and headers are set to en-US.

Possible Solutions

Possible solutions to this bug include:

Using a different input field type: Consider using a different input field type, such as a text field, to avoid this issue.
Formatting the value manually: Format the value manually in the application code to ensure that the correct decimal point separator is used.
Using a library or plugin: Use a library or plugin that provides a decimal type input field with the correct decimal point separator.

Recommendations

Based on the analysis of the bug, the following recommendations are made:

Test the application thoroughly: Test the application thoroughly to ensure that the decimal type input field is working correctly.
Use a different input field type: Consider using a different input field type, such as a text field, to avoid this issue.
Format the value manually: Format the value manually in the application code to ensure that the correct decimal point separator is used.

Future Work

Future work includes:

Investigating the cause of the bug: Investigate the cause of the bug to ensure that it is not related to any other issues in the application.
Testing the application with different locales: Test the application with different locales to ensure that the decimal type input field is working correctly.
Providing a solution to the bug: Provide a solution to the bug, such as using a different input field type or formatting the value manually.
Decimal Type Input Field Shows Wrong Decimal Point Separator: Q&A ====================================================================

Q: What is the issue with the decimal type input field?

A: The issue is that the decimal type input field shows the wrong decimal point separator, specifically the comma (,) instead of the period (.) as expected.

Q: What is the expected behavior of the decimal type input field?

A: The expected behavior of the decimal type input field is to show the correct decimal point separator, which is the period (.) in the United States style (e.g., 300.44).

Q: What are the possible causes of the issue?

A: The possible causes of the issue include:

Incorrect locale settings: The locale settings may be incorrect, which can cause the decimal type input field to show the wrong decimal point separator.
Browser locale and headers: The browser locale and headers may be set to a different locale, which can cause the decimal type input field to show the wrong decimal point separator.
Application code: The application code may be causing the issue, which can be due to a bug or a misconfiguration.

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

Set computer date and number formatting: Set the computer date and number formatting to Belgium.
Set system language default: Set the system language default to English (United States).
Create a decimal field: Create a decimal field.
Enter a number en-us formatted: Enter a number in the United States style (e.g., 300.44).
Save the entry: Save the entry.
Edit the entry: Edit the entry.
Value in the field: The value in the field should show 300,44.

Q: What are the possible solutions to the issue?

A: The possible solutions to the issue include:

Using a different input field type: Consider using a different input field type, such as a text field, to avoid this issue.
Formatting the value manually: Format the value manually in the application code to ensure that the correct decimal point separator is used.
Using a library or plugin: Use a library or plugin that provides a decimal type input field with the correct decimal point separator.

Q: How can I prevent the issue from occurring in the future?

A: To prevent the issue from occurring in the future, follow these steps:

Test the application thoroughly: Test the application thoroughly to ensure that the decimal type input field is working correctly.
Use a different input field type: Consider using a different input field type, such as a text field, to avoid this issue.
Format the value manually: Format the value manually in the application code to ensure that the correct decimal point separator is used.

Q: What are the best practices for handling decimal numbers in web applications?

A: The best practices for handling decimal numbers in web applications include:

Using a consistent decimal point separator: Use a consistent decimal point separator throughout the application.
Formatting numbers manually: Format numbers manually in the application code to ensure that the correct decimal point separator is used.
Testing the application thoroughly: Test the application thoroughly to ensure that the decimal type input field is working correctly.

Q: How can I get help if I am experiencing issues with the decimal type input field?

A: If you are experiencing issues with the decimal type input field, you can get help by:

Checking the documentation: Check the documentation for the application or library you are using to see if there are any known issues or solutions.
Searching online forums: Search online forums, such as Stack Overflow, to see if others have experienced similar issues and have found solutions.
Reaching out to the community: Reach out to the community, such as by posting on a forum or social media, to see if others can provide assistance.