sampotts

While building Plyr (plyr.io) I noticed how fiddly the use of <input type="range"> elements is on touch devices. Having a search around I couldn't find a suitable fix and so created RangeTouch, a small library that improves support on touch devices. Let me know what you think.

So you... work for them?

But comparing Canberra to SF isn't fair. Compare it to Sydney. It's $2k here easily a month for a 2 bed place to rent, depending on the suburb.

Do you mean the progress of playback? This is a native <progress> element. I did have some transitioning on it originally but it felt sluggish. Thanks for the feedback though I'll take a look into it.

Hey there, thanks for the feedback! Good points. I agree, the captions and restart icons do need some work. Easy fix that I can do pretty quickly.

With regards to the tooltips, currently there are hidden labels which are read out by screen readers. If you view the rendered source, you'll see some spans with "sr-only" classes which contain labels that get read out by the likes of voiceover, etc. An option to show these as tooltips would be a good idea though.

Thanks!

Hey there, thanks for the feedback. This has been raised as an issue on GitHub and is on my to-do list.

I'll admit, this is my first open source project and I didn't know what to do license wise. I've now changed it to the MIT license as that seemed the most appropriate? Basically we're not going to sue you if you modify or use it. Frankly I'm happy it's been so well received. Thanks for the feedback!

Thanks for the feedback fellas. I'll look at this. You're totally right that they're both not obvious enough.

Hey Kevin,

Thanks! I've implemented your change in the latest version. It makes sense to check the "input" event rather than "change" as it occurs first. Only downer is no IE10 support.

I'll admit, I did little research other than looking for media players using the same name. There's only so many relevant words or variations of words I could use.