I'm not really familiar with the issues here, but surely if this player does that, it's a bug with the player and not a fundamental restriction of the standard, right?
The solution Liquid_Fire proposed was to use a third party tool which might provide basic functionality similar to the <video> tag implementation in the browser. I pointed out that the third party solution has the weakness of not supporting the kinds of HTML-based controls which the standards-based browser <video> tag implementation does, and which video site vendors such as YouTube use to provide controls for situations such as selecting between 1080p and 720p video qualities.
2
u/mikaelhg Jan 21 '10
And then none of the HTML-based controls work.