Bug: Can't drag the range slider input inside <Dynamic /> component

[zwelhtetyan]

Describe the bug

Range slider input can't slide on Android devices when wrap with <Dynamic /> component. Please check below sandbox demo.

https://stackblitz.com/edit/solidjs-dynamic-component-m1bgckbe?file=src%2Findex.jsx

https://solid-dynamic.vercel.app This is the url deployed the same version in sandbox to test with android devices easily.

Your Example Website or App

https://codesandbox.io/p/devbox/694lr9

Steps to Reproduce the Bug or Issue

---

Expected behavior

Range slider should be able to slide in all devices.

Screenshots or Videos

No response

Platform

• OS: Android
• Browser: Chrome
• Version: version 134.0.6998.135

Additional context

No response

[titoBouzout]

This is a wild android chrome bug when generating input type range dynamically.

Workarounds that fix the problem:

add somewhere

document.addEventListener("touchstart", () => {});

or inlining the event as

<input type="range" on:touchstart={()=>{}}>

I tried to report the bug to chrome but their wizard is broken

---

Im gonna save this here for whenever I can report the bug (edit: filled as https://issues.chromium.org/issues/436887349 )

title:
input type range not draggable in chrome android

steps:

1. create dynamically input type range
2. the slider cannot be dragged

description:
When an input type range like <input type="range"/> is created dynamically, is not draggable. You can click the slider, but you cannot drag it.

additional comments:

Im attaching three files, the only difference between the files are: the broken version, and the weird workarounds.

• lala7.html - it creates an input type range using solid js, and its broken you cannot drag it
• lala8.html - its same as lala7.html but at the top of the file it adds this workaround document.addEventListener("touchstart", () => {});
• lala9.html - its same as lala7.html but it inlines the workaround in the element as <input type=range ontouchstart="()=>{}">

lala7.html.txt
lala8.html.txt
lala9.html.txt

filled upstream https://issues.chromium.org/issues/436887349

[ryansolid]

Honestly because the fix on their side upstream requires no change for us, I don't think it makes sense for us to track it. Closing as there is nothing for us to do here.

[titoBouzout]

chrome just fixed it https://issues.chromium.org/issues/436887349