Follow-up: Confirm Button Disabled Due to Floating-Point Precision Mismatch
I’m following up on my original post regarding the donation confirmation pop-up, where the "Confirm" button remains disabled even when the correct amount is entered. With the help of some AI, I have drafted the following bug report:

Summary of Issue
When entering donation amounts that visually sum to $75.73, the confirmation field fails to validate—even when 75.73 is typed in exactly. The checkmark indicator remains grey, and the "Confirm" button stays disabled.
After inspecting the DOM and running diagnostics in the browser console, I discovered that the issue stems from a floating-point precision mismatch between the calculated Donation Total and the value expected by the confirmation logic.

Technical Findings
Here’s what I observed:
I entered the following donation amounts:
Tithing: 50.73
Fast Offerings: 20.00
Humanitarian Aid: 2.50
General Offerings: 2.50
These values visually sum to $75.73, which is displayed correctly in the UI. However, the underlying amount attribute on the confirmation pop-up is set to 75.72999999999999.
This discrepancy causes a strict comparison to fail when entering 75.73 into the confirmation field.
Console Output:
Input Values: [50.73, 20, 2.5, 2.5]
Raw Sum: 75.72999999999999
Rounded Sum: 75.73
Reported Total (from DOM): 75.72999999999999

Totals do NOT match. Possible floating-point precision issue.

Suggested Fix
To resolve this, I recommend rounding the calculated Donation Total to two decimal places before passing it to the confirmation pop-up. This would eliminate floating-point precision errors and ensure consistent validation.
Example Fix:
const roundedTotal = (Math.round(total * 100) / 100).toFixed(2);
This would ensure the amount attribute reflects the same value users are expected to enter, allowing the checkmark to activate and the button to enable as intended.
Thanks again to the developers and forum moderators for reviewing this. I’m happy to provide further details or test additional scenarios if needed. I hope this helps improve the experience for others encountering the same issue.