fix(sl-range): add value change handler

[timefordroids]

When we update the value for sl-range programmatically, then the active and inactive portions of the track are not updated according to the new value.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/shoelace/shoelace/3TJRoHiM11yFYNxpZCDDrVDaHrN3
✅ Preview: https://shoelace-git-fork-timefordroids-fix-sl-range-va-6dfb8e-shoelace.vercel.app

[claviska]

Is there a reason for requestAnimationFrame here? Seems to work fine without it, but I'm curious to know if it solved a browser-specific issue you discovered.

Good catch on the validity check, too!

[timefordroids]

You're right, it works fine in common cases. But I'm discovered some twitching on my project when the value updated without requestAnimationFrame.

[claviska]

Thanks again. I dug into this and I don't see a reason for RAF in handleInput() or handleValueChange(). I tested in all browsers by manually and programmatically setting values and everything seems smooth. If you're seeing a twitch in your app in the next beta, let's try for a repro so we can narrow it down.

[timefordroids]

Sure. Thank you 👌