> If you want to start a discussion picking a concrete Chrome-only API, I'd encourage it
replySorry, but I don't want to do anything Chrome-only at all. You must have misunderstood my point, as I want cross browser performance. Limiting functionality to one browser is not the point. The main question was if there were things on the road map that were going to be added that would limit use on all browsers. I don't want anything I'm involved with to lock a user into one browser over another. This is no longer 1999 best viewed in Netscape at 800x600 type of nonsense. Otherwise, I have to keep extending on my own. At that point, there's not point in me looking for a 3rd party solve.
Oh I definitely misunderstood! VJS is designed to have a "why not both?" approach for all of these things. Though, to your point, we will never build a core player or set of core functionalities that are not intended to work with all "standard" modern browsers. There are a few maybe obvious asterisks there (e.g. AirPlay for Safari, Chromecast for Chrome, etc.), but that's our general approach. That said, we don't want to preclude folks from being able to take advantage of fancy, browser-specific features if they so choose (and we may have "official" support for some of these).
reply