W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2019

Re: [mediacapture-main] Clarification needed on HTMLMediaElement attributes that carry over (#599)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 May 2019 15:17:42 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-496562096-1559056661-sysbot+gh@w3.org>
> But what should be returned the third time?

`0.5`, because [html](https://html.spec.whatwg.org/multipage/media.html#dom-media-playbackrate) says *"on getting it must return the last value it was set to, ..."*, which was `0.5`.

[Mediacapture](https://w3c.github.io/mediacapture-main/getusermedia.html#mediastreams-in-media-elements) says: *"On setting: ignored. On getting: return 1.0"*. It doesn't say *"set [state] to 1"*.

This might have been clearer had the HTML spec used internal slots, but I think the principle still holds, that mediacapture does not say to alter any (internal and implicit) state.

So as soon as the element is no longer associated with a stream, we should revert to html.

Now, it continues: *"Therefore, this attribute MUST always have the value 1.0 and any attempt to alter it MUST be ignored. Note that this also means that the ratechange event will not fire."* - but taken together, this appears to be talking about the "attribute" as an API, i.e. net-JS-observable requirements.

That's my reading of the current language, but I agree could be clearer. Thoughts?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/599#issuecomment-496562096 using your GitHub account
Received on Tuesday, 28 May 2019 15:17:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:23 UTC