[Bug]: Slider does not update when iPad keyboard closes and input field loses focus

[lehelen19]

Code of conduct

• I agree to follow this project's code of conduct.

Impacted component(s)

sp-slider

Library version

1.7.0

Expected behavior

Slider should update its value once the iPad keyboard has closed and the input field has lots its focus.

Actual behavior

Slider does not update its value. See CCEX-232631.

Repro: iOS

iPad Mini 5Gen, iOS 26 Dev Beta 9, 3 GB Ram

iPad mini 6th gen , IOS 18.5

Screenshots

Untitled.mp4

What browsers are you seeing the problem in?

No response

How can we reproduce this issue?

1. Go to the editable slider storybook
2. Input a change into the input field
3. Close the keyboard
4. Observe how the focus is lost but the slider doesn't update

Sample code or abstract reproduction which illustrates the problem

No response

Severity

SEV 2

Logs taken while reproducing problem

No response

Would you like to track this issue in Jira?

• Yes, please tell me the ticket number!

[najikahalsema]

SWC-1341

[Rajdeepc]

Hi @lehelen19 I see you have marked this as SEV 2 but I feel this would be more of a SEV 3 or SEV 4. This is a UX consistency mismatch on mobile, but it's not critical.
Coming to this issue, I triaged it and found that this isn’t a straightforward fix — the issue stems from how iOS handles its floating and split keyboards. When the keyboard appears, iOS dynamically resizes the visualViewport without consistently dispatching focus or resize events that web apps can reliably hook into. This makes it hard to detect exactly when the keyboard is dismissed or when the viewport returns to its original state.

Because of this, even well-tested approaches (using visualViewport or scroll detection) behave inconsistently across iPad models and iOS versions. It’s more of a platform-level quirk than something fixable purely in our component layer.

A possible workaround is to rely on manual commit triggers (e.g., blur, submit, or explicit “Done” button actions) instead of auto-committing on keyboard close. If this becomes a recurring issue, it would be a good idea to handle it via a custom controller at the app level rather than in the component itself.

I’d suggest delegating this for further exploration when we have time to test across multiple iOS devices and configurations.