Input System: negative and NaN values can be entered and saved in the "Location Accuracy" and "Location Distance Threshold" settings fields, while the scripting API corrects the same values to 0

Steps to reproduce:

1. Create a new project on 6000.7.0a6
2. Install the Input System package via "Window > Package Manager" if it is not already installed
3. Right-click "Assets" in the Project window, select "Create > Folder" and name it Editor
4. Right-click the Editor folder, select "Create > Scripting > Empty C# Script" and name it LocationSettingsProbe
5. Open the file, replace its entire contents with the script given below, save, and wait for compilation to finish with no Console errors
6. Open "Edit > Project Settings > Input System Package" and select "Settings"
7. Click "Create settings asset"
8. Type -5 into "Location Accuracy" and press "Return"
9. Type -12.5 into "Location Distance Threshold" and press "Return"
10. In the main menu select "Tools > Log Location Settings" and read the two values in the Console
11. Type NaN into "Location Accuracy", press "Return", then select "Tools > Log Location Settings" again
12. Select "Tools > Assign -5 Through The API" and read the value it logs
13. Compare the value logged in step 11 against the one logged in step 9
14. Save the project, open the settings asset named at the top of the "Input System Package" page in a text editor, and read the same two values

Actual results: Values entered in the settings window are stored exactly as typed:

The same value assigned through the scripting API is corrected. Step 11 logs 0 after assigning -5, while step 9 logs -5 for the value typed into the window. So the same setting accepts a value on one path and rejects it on the other.

Expected results: The settings window applies the same correction as the scripting API: negative values and non-finite values are corrected to 0 before being stored.

Reproducible with versions: 6.7.0 (6000.7.0a6)

Can’t test with versions: All other streams as "Location Accuracy" and "Location Distance Threshold" are new in Input System 6.7.0. Neither the fields nor this part of the settings UI exist in 1.20.0.

Tested on (OS): MacBook Pro - Tahoe 26.6.2

Notes: Script for step 5

using UnityEditor;
using UnityEngine;
using UnityEngine.InputSystem;public static class LocationSettingsProbe
{
    [MenuItem("Tools/Log Location Settings")]
    public static void LogLocationSettings()
    {
        var s = InputSystem.settings;
        Debug.Log($"locationAccuracy = {s.locationAccuracy:R}");
        Debug.Log($"locationDistanceThreshold = {s.locationDistanceThreshold:R}");
    }    [MenuItem("Tools/Assign -5 Through The API")]
    public static void AssignNegativeThroughApi()
    {
        InputSystem.settings.locationAccuracy = -5f;
        Debug.Log($"after assigning -5 via the API, locationAccuracy = {InputSystem.settings.locationAccuracy:R}");
    }
}