On Github mmcc / slides-vjs-5-peak
A shim is required, so a conscious decision is required.
Die IE8. Die.
To view this video please enable JavaScript, and consider upgrading to a web browser that supports HTML5 video
.vjs-skin-hotdog-stand { color: #FF0000; } .vjs-skin-hotdog-stand .vjs-control-bar { background: #FFFF00; } .vjs-skin-hotdog-stand .vjs-play-progress { background: #FF0000; }
Tab order isn't an issue anymore! Woo!
I know none of you have experienced technical debt...
Only really an issue in development
var Component = require('../component.js'); var LiveDisplay = Component.extend({ /* */ }); var Button = require('../button.js'); var FullscreenToggle = Button.extend({ /* */ });
But wait! There's more!
import Component from '../component.js'; class LiveDisplay extends Component { /* */ }; let foo = 'bar'; const thing = 'will not change'; let { foo, bar, bat } = someObject; let templateStr = `calling all ${peopleType}`; let square = a => a * a;
Via the Babelify Browserify transform
Captions are harder than you think. Native and / or Flash...
(╯°□°)╯︵ ┻━┻
~50 lines of code to parse a cue
Accessibility is always important, but thanks to requirements, everyone's taking notice.
We're working on bundling VTT.js for robust WebVTT support.
Mmmm...nothing says "sexy" like "streamlined deployment processes"
Removed aggressive object property mangling (Closure Compiler)
You mean videojs.b and videojs.A don't exist anymore?!
Actual guidelines for writing and publishing skins / plugins
Because package managers installed with a package manager are dumb.
Yeah. I said it.
Thoughts, concerns, criticisms? Open an issue!