Skip to content

Conversation

@viniciussoares
Copy link
Contributor

@viniciussoares viniciussoares commented Dec 5, 2025

On iOS Safari, the native range input thumb appears as a white ball in the center of the auto-close knob component, overlaying the custom UI.

Fix

Hide the range input on iOS Safari using a @supports feature query that targets WebKit on iOS.

Before After

@jzimdars
Copy link
Member

jzimdars commented Dec 6, 2025

I haven't been able to reproduce this. Is it only happening in a particular version of Mobile Safari? I'm on iOS 26.1.

I don't love that this uses a generic @supports query to target Safari instead of querying for this specific feature. Dumb question: did you try -webkit-appearance: none;. Sometimes that's still effective even when appearance: none should work.

@foucist
Copy link

foucist commented Dec 6, 2025

It's also not mobile specific, I get this in desktop on Safari 17.6
Screen Shot 2025-12-06 at 12 37 18 PM.

…forward opacity: 0 on the slider element
@viniciussoares
Copy link
Contributor Author

I haven't been able to reproduce this. Is it only happening in a particular version of Mobile Safari? I'm on iOS 26.1.

I don't love that this uses a generic @supports query to target Safari instead of querying for this specific feature. Dumb question: did you try -webkit-appearance: none;. Sometimes that's still effective even when appearance: none should work.

@jzimdars I tried another approach using opacity: 0 directly on .knob__slider and it works! In my case it happens on iOS 17.6.1.

It's also not mobile specific, I get this in desktop on Safari 17.6

@foucist Can you test with this new commit?

@jzimdars
Copy link
Member

jzimdars commented Dec 8, 2025

I don't have an older version of Safari to test with but I can confirm the opacity: 0 doesn't break the intended behavior in Firefox and Chrome.

@jorgemanrubia
Copy link
Member

So this one is good to merge @jzimdars?

@jzimdars
Copy link
Member

@jorgemanrubia I was hoping that @foucist would confirm it fixed the issue for him but even if it doesn't, it's harmless and ok to merge.

@jzimdars jzimdars merged commit 2a17976 into basecamp:main Dec 11, 2025
4 checks passed
@foucist
Copy link

foucist commented Dec 12, 2025

Sorry, I got stuck with dev env issues so I wasn't able to test it locally. Looks good to me on app.fizzy.do now.

@jzimdars
Copy link
Member

No worries. Thanks for looking!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants