I'm pushing forward on the video.js player mode in TimedMediaHandler, which gives us some advantages over the old Kaltura-based MwEmbedPlayer widget:

* works on mobile * a cleaner look n' feel * cleaner, more modern, better maintained player infrastructure code

Big thanks to Derk-Jan for tons of work getting the video.js mode into the codebase, and to Paladox for lots of bug reports and patches. :)

Once some more improvements go in, I'd like to integrate it with BetaFeatures for testing on the production sites by some "real users" sometime in the coming weeks... Paladox is working on a patch for that now. May also be able to deploy video.js on mobile first, where we just have "bare" audio players and raw video links (or on iOS, nothing that works).

There's a lot of little bugs to work out, mostly straightforward looking and a few scary-looking, but we also will want to improve the UI skin for the player.

On the UI end, I've brainstormed a little on my own and made some mockups of what a player UI that scales down to phones and up to desktops might look like: * https://upload.wikimedia.org/wikipedia/mediawiki/2/27/TimedMediaHandler_vide... Beware the icons are wrong-colored screenshots from FontAwesome's demo pages; it's mainly intended to look at the layout. ;)

I'm trying to keep the number of controls down while still providing access to the key features of playback, caption & quality control, and further info/license/download/sharing/whatnot...

It might be wise to think more about how it would look to integrate this player into the media viewer infrastructure for photo viewing -- is there danger of overlapping icons? Should the 'share' and 'info' and 'download' stuff be outsourced into the media viewer dialog?

But I'll want it to work for inline playback as well, both for audio files and in the future for migrating things from autoplayed looped silent GIFs to autoplayed looped silent WebM videos. :)

-- brion