Setting slider max to Infinity can crash the browser or throw an error

[hahn-kev]

Describe the bug

If you set <Slider.Root max={Infinity}/> either directly, or though error, in Firefox the tab will hang, and Chrome will report an error with max array size, which is how I was able to track down the issue. Ideally bits would throw an error to avoid crashing the tab.

In my case I was creating an audio player, and the audio element set duration as Infinity.

Reproduction

https://stackblitz.com/edit/xvfvdpk8?file=src%2Froutes%2F%2Bpage.svelte

Logs

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
    Memory: 7.22 GB / 31.69 GB
  Binaries:
    Node: 20.18.1 - ~\AppData\Local\nvs\default\node.EXE
    npm: 10.8.2 - ~\AppData\Local\nvs\default\npm.CMD
    pnpm: 10.12.3 - ~\AppData\Local\nvs\default\pnpm.CMD
    bun: 1.2.2 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (137.0.3296.93)
    Internet Explorer: 11.0.26100.1882

Severity

annoyance

[huntabyte]

We can definitely throw an error, but in the case of an ARIA slider, using it with Infinity doesn't make sense.

ARIA slider requires finite bounds: The ARIA slider role expects meaningful aria-valuemin and aria-valuemax attributes. Infinite values break this semantic contract.

Perhaps there is another component we could add that would support this because I can totally see why one might think this is the right component for a live audio feed or whatever you're using it for!