W3C home > Mailing lists > Public > public-media-capture@w3.org > October 2014

[Bug 25777] Capabilities seem under specified

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Oct 2014 14:21:01 +0000
To: public-media-capture@w3.org
Message-ID: <bug-25777-5753-eUPaMvHEW1@http.www.w3.org/Bugs/Public/>

Jan-Ivar Bruaroey [:jib] <jib@mozilla.com> changed:

           What    |Removed                     |Added
                 CC|                            |jib@mozilla.com

--- Comment #7 from Jan-Ivar Bruaroey [:jib] <jib@mozilla.com> ---
While examples are nice, I would argue they're no replacement for

Are capabilities accurate?

While it is possible to deduce from the applyConstraints algorithm [1] that
capabilities are allowed to be a super-set of what the UA supports, I find no
mention of this where Capabilities is defined [2].

I've read the definition a couple of times, and even though it uses the word
"subset" four times in one paragraph, it still seems to equate what the
capabilities read with what "the UA supports", which doesn't allow for
capabilities to be either-or (e.g. super framerate OR super resolution).

I think it would help implementations if the spec stated that returned
capabilities must a set or super-set of what the UA supports.

Are capabilities constant?

I find conflicting text on this in the spec:

"The UA may choose new settings for the Capabilities of the object at any time.
When it does so it must attempt to satisfy the current Constraints, in the
manner described in the algorithm above." [2]


"Source capabilities are effectively constant. Applications should be able to
depend on a specific source having the same capabilities for any session." [3]

[2] http://w3c.github.io/mediacapture-main/getusermedia.html#capabilities
[3] http://w3c.github.io/mediacapture-main/getusermedia.html#terminology

You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 9 October 2014 14:21:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:30 UTC