Thursday, 26 February 2015
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- Re: [mediacapture-main] Lack of timeout / cancellation leads to UI inconsistencies
Monday, 23 February 2015
Saturday, 21 February 2015
- Re: [mediacapture-main] MediaDeviceInfo.label and groupId are unnecessarily nullable
- Re: [mediacapture-main] enumerateDevices' access model is unclear
- Re: [mediacapture-main] MediaDeviceInfo.label and groupId are unnecessarily nullable
- Re: [mediacapture-main] enumerateDevices' access model is unclear
- Re: [mediacapture-main] MediaDeviceInfo.label and groupId are unnecessarily nullable
- Re: [mediacapture-main] MediaDeviceInfo.label and groupId are unnecessarily nullable
- [mediacapture-main] enumerateDevices' access model is unclear
- [mediacapture-main] MediaDeviceInfo.label and groupId are unnecessarily nullable
Thursday, 19 February 2015
- Re: [mediacapture-main] Bugs which require someone to fix things
- Re: [mediacapture-main] Need to specify action on constraints that give no value.
Wednesday, 18 February 2015
- Re: [mediacapture-main] Need to specify action on constraints that give no value.
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] Need to specify action on constraints that give no value.
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] Fix language around advanced algorithm to be unambiguous.
- Re: [mediacapture-main] Fix language around advanced algorithm to be unambiguous.
- Re: [mediacapture-main] Fix language around advanced algorithm to be unambiguous.
- Re: [mediacapture-main] Fix language around advanced algorithm to be unambiguous.
- [mediacapture-main] new commits pushed by adam-be
- [mediacapture-main] new commits pushed by adam-be
- Closed: [mediacapture-main] add hotlinks to the definition of "constraint" under applyConstraints
- Re: [mediacapture-main] Need to specify action on constraints that give no value.
- Re: [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
Monday, 16 February 2015
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] links to github for issues, mailing list for discussion
- [mediacapture-main] new commits pushed by adam-be
- Re: [mediacapture-main] Markup fixes
Saturday, 14 February 2015
Friday, 13 February 2015
- Re: [mediacapture-main] Need to specify action on constraints that give no value.
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- [mediacapture-main] Pull Request: links to github for issues, mailing list for discussion
- Re: [mediacapture-main] Markup fixes
- Re: [mediacapture-main] A practical algorithm for constraint resolution needs to be described.
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
- [mediacapture-main] Need to specify action on constraints that give no value.
- Re: [mediacapture-main] A practical algorithm for constraint resolution needs to be described.
- [mediacapture-main] No way to represent a boolean Capability that can be turned on or off
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
Thursday, 12 February 2015
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
- [mediacapture-main] new commits pushed by alvestrand
- Closed: [mediacapture-main] What's the fitness distance if no ideal is specified?
- Re: [mediacapture-main] add hotlinks to the definition of "constraint" under applyConstraints
- [mediacapture-main] Pull Request: add link to constraints def in selectsettings
- Re: [mediacapture-main] add hotlinks to the definition of "constraint" under applyConstraints
- Re: [mediacapture-main] Fix language around advanced algorithm to be unambiguous.
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
- Re: [mediacapture-main] define fitness distance when ideal is not specified
- Re: [mediacapture-main] A practical algorithm for constraint resolution needs to be described.
- Re: [mediacapture-main] DeviceID, kind and label needs to be aligned with capabilities
- Closed: [mediacapture-main] DeviceID, kind and label needs to be aligned with capabilities
- [mediacapture-main] new commits pushed by alvestrand
Wednesday, 11 February 2015
Tuesday, 10 February 2015
- Re: [mediacapture-main] avoid MUST for non-UA requirement in SelectSettings definition.
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- Re: [mediacapture-main] define fitness distance when ideal is not specified
- Re: [mediacapture-main] remove sentence about sourceType change (doesn't happen)
- [mediacapture-main] new commits pushed by burnburn
- Re: [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
- Re: [mediacapture-main] clarify how a constraint is read
- Re: [mediacapture-main] Should attach the media element to the MediaStream object
- Closed: [mediacapture-main] Should attach the media element to the MediaStream object
- Re: [mediacapture-main] Should attach the media element to the MediaStream object
- Re: [mediacapture-main] clarify how a constraint is read
- Re: [mediacapture-main] prohibit multiple getUserMedia() calls sharing the same capture device
- Closed: [mediacapture-main] prohibit multiple getUserMedia() calls sharing the same capture device
- [mediacapture-main] new commits pushed by adam-be
- Re: [mediacapture-main] Should attach the media element to the MediaStream object
- Re: [mediacapture-main] Should attach the media element to the MediaStream object
- [mediacapture-main] Pull Request: avoid MUST for non-UA requirement in SelectSettings definition.
- Re: [mediacapture-main] DeviceID, kind and label needs to be aligned with capabilities
- Re: [mediacapture-main] Should attach the media element to the MediaStream object
- Closed: [mediacapture-main] Improve description of EventHandler attributes
- [mediacapture-main] new commits pushed by burnburn
- Re: [mediacapture-main] reword event handler descriptions to make their circumstances clearer
- [mediacapture-main] Should attach the media element to the MediaStream object
- Re: [mediacapture-main] Cababilities need to clearly specify that they are constant over time
- [mediacapture-main] new commits pushed by burnburn
Monday, 9 February 2015
- [mediacapture-main] Pull Request: use proper text for link-less applyConstraints
- [mediacapture-main] Pull Request: clarify how a constraint is read
- Re: [mediacapture-main] remove sentence about sourceType change (doesn't happen)
- Re: [mediacapture-main] define fitness distance when ideal is not specified
- [mediacapture-main] Pull Request: remove sentence about sourceType change (doesn't happen)
- Re: [mediacapture-main] DeviceID, kind and label needs to be aligned with capabilities
- [mediacapture-main] new commits pushed by burnburn
Sunday, 8 February 2015
- [mediacapture-main] new commits pushed by burnburn
- Re: [mediacapture-main] reword event handler descriptions to make their circumstances clearer
Friday, 6 February 2015
- Re: [mediacapture-main] DeviceID, kind and label needs to be aligned with capabilities
- Re: [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
- Re: [mediacapture-main] define fitness distance when ideal is not specified
- Re: [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
- Re: [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
- [mediacapture-main] Pull Request: settings (plural) dictionary
- [mediacapture-main] Pull Request: define fitness distance when ideal is not specified
- [mediacapture-main] new commits pushed by burnburn
- Closed: [mediacapture-main] constraint properties should not be scoped to "source" only
- [mediacapture-main] new commits pushed by burnburn
- Re: [mediacapture-main] constraint properties should not be scoped to 'source' only; close #69
- [mediacapture-main] Fitness distance must interpret plain values in advanced array as exact.
Thursday, 5 February 2015
- Re: [mediacapture-main] Lack of timeout / cancellation leads to UI inconsistencies
- Re: [mediacapture-main] What's the fitness distance if no ideal is specified?
Wednesday, 4 February 2015
- [mediacapture-main] Lack of timeout / cancellation leads to UI inconsistencies
- [mediacapture-main] new commits pushed by adam-be
- [mediacapture-main] Pull Request: Fix language around advanced algorithm to be unambiguous.
Tuesday, 3 February 2015
- [mediacapture-main] What's the fitness distance if no ideal is specified?
- Re: [mediacapture-main] prohibit multiple getUserMedia() calls sharing the same capture device
- Re: [mediacapture-main] prohibit multiple getUserMedia() calls sharing the same capture device
- Re: [mediacapture-main] prohibit multiple getUserMedia() calls sharing the same capture device
- Re: [mediacapture-main] Tweaks to new apply constraints algo
- Closed: [mediacapture-main] Normative text in "Terminology" section
Monday, 2 February 2015
- [mediacapture-main] new commits pushed by adam-be
- Closed: [mediacapture-main] Do we need MediaStreamError.constraintName?
- Re: [mediacapture-main] Do we need MediaStreamError.constraintName?
- Closed: [mediacapture-main] MediaStream: 'input", "output", and number of "consumers"
- Re: [mediacapture-main] MediaStream: 'input", "output", and number of "consumers"
- Closed: [mediacapture-main] Clarification in "Introduction" section
- Re: [mediacapture-main] Clarification in "Introduction" section
- Re: [mediacapture-main] Aren't not understood constraints ignored?
- Closed: [mediacapture-main] Aren't not understood constraints ignored?
- Re: [mediacapture-main] Tweaks to new apply constraints algo
- Re: [mediacapture-main] Explanation of constraints in GUM call
- Closed: [mediacapture-main] Explanation of constraints in GUM call
- Re: [mediacapture-main] Do we need MediaStreamError.constraintName?
- Re: [mediacapture-main] Aren't not understood constraints ignored?
- [mediacapture-main] Pull Request: Tweaks to new apply constraints algo
- Re: [mediacapture-main] Explanation of constraints in GUM call