input[type=range] fix on Chrome#1282
Conversation
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Regarding the use of a CodePen I'm not against it atm but I'm afraid it would be complicated to maintain for each version. |
You're right, during the write of the Codepen, I was asking myself on how to remember to update this Codepen, I'll implement your idea. |
|
@MewenLeHo This PR can be interesting for you regarding the sliders prototypes you're developing. |
6659905 to
4ee804f
Compare
4ee804f to
e8ad134
Compare
|
FWIW this example could be lighter on the JS-side by using a CSS custom property, here's an example on CodePen. |
|
Hi @ffoodd, Thanks for the comment, I tried to take the CodePen into account, it kindly dedupes the CSS code which is way better. Do you think it's worth to integrate the explanation in Bootstrap directly ? |
|
You may suggest it for sure, but I dont know if it'll be merged 🙂 |
|
Let's wait for twbs/bootstrap#37499 ! |
|
Kudos, SonarCloud Quality Gate passed! |
|
Closing it. Wait for twbs/bootstrap#37499. If accepted in Bootstrap it will be introduced in Boosted automatically. If not, we will recreate a PR here. |









Fixes #1264
https://deploy-preview-1282--boosted.netlify.app/docs/5.2/forms/range/
It fixes the thumb display on Chrome and add an explaination to implement the runnable track on Chrome.