On Tue, Aug 24, 2010 at 7:43 PM, Philip Jägenstedt <span dir="ltr"><<a href="mailto:philipj@opera.com" target="_blank">philipj@opera.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Tue, 24 Aug 2010 10:24:35 +0200, Ian Hickson <<a href="mailto:ian@hixie.ch" target="_blank">ian@hixie.ch</a>> wrote:</div><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Given that, it wouldn't be a big problem to let modification of src<br>
attributes on source elements trigger resource selection, you won't get<br>
the 3-2-1 problem I mentioned earlier.<br>
</blockquote>
<br>
I don't really understand what use case this would solve.<br>
</blockquote>
<br></div>
Neither do I, I'm just saying that it's easy to do if necessary.</blockquote><div><br>I was running through all the properties that can possibly be changed in JavaScript and checking which effects they have in all browsers, i.e. what events they call etc. I wasn't aware that authors are discouraged from changing @src on <source>.<br>
<br><br><div class="gmail_quote">On Tue, Aug 24, 2010 at 6:24 PM, Ian Hickson <span dir="ltr"><<a href="mailto:ian@hixie.ch" target="_blank">ian@hixie.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<br>
On Sat, 24 Jul 2010, Silvia Pfeiffer wrote:<br>
><br>
> There is definitely a spec bug, because different locations of the spec<br>
> say diverging things.<br>
<br>
For the record, when the spec contradicts itself, and one part is<br>
normative (such as the algorithm here) and another is non-normative (such<br>
as the definitions here) then always assume the normative part is wrong. I<br>
often forget to update the non-normative parts.<br></blockquote><div><br>You mean: the normative part is right, I assume?<br>Thanks for this clarification - I was indeed unaware of the history of changes.<br> <br><br></div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
On Mon, 26 Jul 2010, Silvia Pfeiffer wrote:<br>
><br>
> I now wonder about the intention of play() (and also of pause()). As I<br>
> understood it, they are both meant to reload the media resource if<br>
> @currentSrc has changed, similar to what load() is supposed to do.<br>
<br>
I do not believe that has ever been the intent.<br></blockquote><div><br><br>Both descriptions of play() and pause() have a "loading the media resource" in them. <br>
<dl><dt><var title="">media</var> . <code title="dom-media-play"><a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-media-play" target="_blank">play</a></code>()</dt><dd>
<p>Sets the <code title="dom-media-paused"><a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-media-paused" target="_blank">paused</a></code> attribute
to false, loading the <a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#media-resource" target="_blank">media resource</a> and beginning
playback if necessary. If the playback had ended, will restart it
from the start.</p>
</dd><dt><var title="">media</var> . <code title="dom-media-pause"><a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-media-pause" target="_blank">pause</a></code>()</dt><dd>
<p>Sets the <code title="dom-media-paused"><a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-media-paused" target="_blank">paused</a></code> attribute
to true, loading the <a href="http://www.whatwg.org/specs/web-apps/current-work/complete.html#media-resource" target="_blank">media resource</a> if necessary.</p>
</dd></dl>I assumed that if the @currentSrc had changed, that would trigger loading the new media resource, too. If that is not the intention, maybe the non-normative description should point out that it only triggers loading the media resource when the @src attribute is being set for the very first time. Though, to be honest, I don't really see a difference between setting @src through JavaScript for the first time (which IIUC also has a NETWORK_EMPTY state) and re-setting it again a subsequent time - IMHO both should consistently either include the media resource loading or exclude it.<br>
<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
On Tue, 27 Jul 2010, Silvia Pfeiffer wrote:<br>
><br>
> Sure, but this is only a snippet of an actual application. If, e.g., you<br>
> want to step through a list of videos (maybe an automated playlist)<br>
> using script and you need to provide at least two different formats with<br>
> <source>, you'd want to run this algorithm frequently.<br>
<br>
Just have a bunch of <video>s in the markup, and when one ends, hide it<br>
and show the next one. Don't start dynamically manipulating <source><br>
elements, that's just asking for pain.<br>
<br>
If you really must do it all using script, just use canPlayType and the<br>
<video src=""> attribute, don't mess around with <source>.<br></blockquote><div><br>Thanks for adding that advice. I think it's important to point that out.<br><br>Cheers,<br>Silvia.<br><br>
</div></div></div></div>