5 ms·
Sorry but this experience is badly broken in iOS and highlights yet again why native controls are always preferable over custom controls for compatibility. Also
by 10dpd 14y ago
Sorry but this experience is badly broken in iOS and highlights yet again why native controls are always preferable over custom controls for compatibility. Also, don't forget about enabling accessibility by using ARIA.
- zootm 14y agoSimilar on Android; the widget behaves perfectly, which is ironically a poor experience on mobile. Looks like it would be very nice on a desktop though!
- repsilat 14y agoShould these sorts of widgets be the default implementation of those types of controls in desktop browsers? As long as they can be done with the same input information, this sort of input seems like a "user preference" issue.
- sourc3 14y agoI can't even scroll the list on iPad not sure if everyone experiencing the same.
- repsilat 14y agoYeah, that's why you do it on the client-side. If the widget doesn't work on an iPad then an iPad browser shouldn't default those controls to that widget. A desktop browser could, though Nobody would be worse off, and nobody would be the wiser (except the user).