w3c/mst-content-hint issues and pull requests

#57 - Improve markup of enumeration tables

Pull Request - State: open - Opened by dontcallmedom about 2 years ago

#56 - Add health warning on "text" constraint

Pull Request - State: open - Opened by alvestrand over 2 years ago - 2 comments
Labels: Discuss at Next Meeting

#55 - Comments and request from APA review

Issue - State: open - Opened by becka11y almost 3 years ago
Labels: a11y-needs-resolution, Discuss at Next Meeting

#54 - Fix suspected copy/paste error

Pull Request - State: closed - Opened by eladalon1983 almost 3 years ago - 1 comment

#53 - Improve Abstract

Pull Request - State: closed - Opened by alvestrand about 3 years ago

#52 - Upgrade automatic TR publication set up

Pull Request - State: closed - Opened by dontcallmedom over 3 years ago

#51 - PING Review

Issue - State: open - Opened by kdeqc almost 4 years ago
Labels: privacy-tracker

#50 - Client/server-side question

Issue - State: closed - Opened by kdeqc almost 4 years ago - 2 comments

#49 - Improve respec autolinking

Pull Request - State: closed - Opened by dontcallmedom almost 4 years ago

#48 - Change "speechRecognition" to "speech-recognition"

Pull Request - State: closed - Opened by alvestrand almost 4 years ago - 2 comments

#47 - Why are arbitrary values disallowed for hints?

Issue - State: closed - Opened by kenchris almost 4 years ago - 5 comments
Labels: question, tag-tracker

#46 - speechRecognition should be "speech-recognition"

Issue - State: closed - Opened by kenchris almost 4 years ago
Labels: tag-tracker

#45 - Abstract: less jargon?

Issue - State: closed - Opened by samuelweiler almost 4 years ago

#44 - Wide review

Issue - State: closed - Opened by caribouW3 almost 4 years ago - 2 comments

#43 - Fix links to Audio/Video Content Hints sections

Pull Request - State: closed - Opened by travisleithead about 4 years ago - 2 comments

#42 - Who's got permission to configure this repo?

Issue - State: closed - Opened by alvestrand about 4 years ago - 1 comment

#41 - Add Security and Privacy Considerations

Pull Request - State: closed - Opened by alvestrand about 4 years ago
Labels: Editors can integrate

#40 - Added the speechRecognition contentHint for machine recognition of speech

Pull Request - State: closed - Opened by sjdallst about 4 years ago

#39 - Differentiate between speech for human and machine consumption

Issue - State: closed - Opened by sjdallst about 4 years ago - 8 comments

#38 - Create security-privacy-questionnaire.md

Pull Request - State: closed - Opened by alvestrand about 4 years ago

#37 - Default degradationPreference value?

Issue - State: open - Opened by henbos over 4 years ago - 1 comment

#36 - What is the value of degradationPreference over time? (replaceTrack, contentHint setter)

Issue - State: open - Opened by henbos over 4 years ago - 3 comments
Labels: Ready for PR, Editorial

#35 - highly detailed text in video content

Issue - State: open - Opened by aphillips over 4 years ago - 2 comments
Labels: Ready for PR

#34 - chore: fix ReSpec markdown error

Pull Request - State: closed - Opened by sidvishnoi over 4 years ago - 1 comment

#33 - degradationPreference is under-specified

Issue - State: open - Opened by aboba over 4 years ago - 4 comments
Labels: Test needed

#32 - Add conformance section

Pull Request - State: closed - Opened by tidoust over 4 years ago - 1 comment

#31 - Add description of behaviors triggered by contentHint

Pull Request - State: closed - Opened by alvestrand over 4 years ago - 6 comments

#30 - Permanence issues

Issue - State: open - Opened by jan-ivar almost 5 years ago - 1 comment
Labels: TPAC 2019

#29 - Lack of normative testable steps

Issue - State: open - Opened by jan-ivar almost 5 years ago - 2 comments
Labels: Test needed

#28 - Reduncancy and lack of normative clarity around interaction with constraints

Issue - State: closed - Opened by jan-ivar almost 5 years ago - 2 comments
Labels: CR blocking, TPAC 2019

#27 - Set up automatic quality check and automatic publication with Echidna

Pull Request - State: closed - Opened by dontcallmedom over 5 years ago

#26 - Repo needs Travis CI

Issue - State: closed - Opened by alvestrand about 6 years ago

#25 - Add "text" content-hint value

Pull Request - State: closed - Opened by alvestrand about 6 years ago

#24 - Interaction with degradationPreference

Issue - State: closed - Opened by aboba about 6 years ago - 3 comments
Labels: CR blocking, Ready for PR

#23 - Adding "text" as a content-hints value

Issue - State: closed - Opened by aboba about 6 years ago - 2 comments

#22 - Intent to Migrate to WebRTC Working Group

Issue - State: closed - Opened by dontcallmedom over 6 years ago - 3 comments

#22 - Intent to Migrate to WebRTC Working Group

Issue - State: closed - Opened by dontcallmedom over 6 years ago - 3 comments

#21 - Possible values, and are multiple values useful?

Issue - State: closed - Opened by jesup over 7 years ago - 8 comments

#21 - Possible values, and are multiple values useful?

Issue - State: closed - Opened by jesup over 7 years ago - 8 comments

#20 - Maybe s/fluid/motion/ ?

Issue - State: closed - Opened by jan-ivar over 7 years ago - 6 comments

#20 - Maybe s/fluid/motion/ ?

Issue - State: closed - Opened by jan-ivar over 7 years ago - 6 comments

#19 - Gather interest from browser vendors/web developers.

Issue - State: closed - Opened by pbos over 7 years ago - 4 comments

#19 - Gather interest from browser vendors/web developers.

Issue - State: closed - Opened by pbos over 7 years ago - 4 comments

#18 - Why not RTCRtpSender?

Issue - State: closed - Opened by martinthomson over 7 years ago - 23 comments

#18 - Why not RTCRtpSender?

Issue - State: closed - Opened by martinthomson over 7 years ago - 23 comments

#17 - When does the browser act on changes?

Issue - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#17 - When does the browser act on changes?

Issue - State: closed - Opened by martinthomson over 7 years ago - 5 comments

#16 - Use an enum

Issue - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#16 - Use an enum

Issue - State: closed - Opened by martinthomson over 7 years ago - 3 comments

#15 - Fix repo link

Issue - State: closed - Opened by domenic over 7 years ago - 1 comment

#14 - Since the enums are not used, they can be removed

Issue - State: closed - Opened by domenic over 7 years ago

#14 - Since the enums are not used, they can be removed

Issue - State: closed - Opened by domenic over 7 years ago

#13 - Processing model should be algorithms, not "valid values"

Issue - State: closed - Opened by domenic over 7 years ago - 1 comment

#13 - Processing model should be algorithms, not "valid values"

Issue - State: closed - Opened by domenic over 7 years ago - 1 comment

#12 - Upload illustrative quantization image

Issue - State: closed - Opened by pbos over 7 years ago

#12 - Upload illustrative quantization image

Issue - State: closed - Opened by pbos over 7 years ago

#11 - Use `partial interface` instead of `interface` with `// ...`

Issue - State: closed - Opened by domenic over 7 years ago

#11 - Use `partial interface` instead of `interface` with `// ...`

Issue - State: closed - Opened by domenic over 7 years ago

#10 - Grammar, company name and url, clear up confusing sentence.

Pull Request - State: closed - Opened by Victorystick over 7 years ago - 1 comment

#9 - Is "content type" confusing with the Content-Type header?

Issue - State: closed - Opened by domenic over 7 years ago - 5 comments

#9 - Is "content type" confusing with the Content-Type header?

Issue - State: closed - Opened by domenic over 7 years ago - 5 comments

#8 - Is the "media" prefix necessary?

Issue - State: closed - Opened by domenic over 7 years ago

#8 - Is the "media" prefix necessary?

Issue - State: closed - Opened by domenic over 7 years ago

#7 - Figure out how to get cross-linking working to the various IDL interfaces and attributes mentioned

Issue - State: closed - Opened by domenic over 7 years ago - 2 comments

#6 - Don't use InterfaceName.attribute notation

Issue - State: closed - Opened by domenic over 7 years ago

#5 - Add a link to the spec from this repo

Issue - State: closed - Opened by domenic over 7 years ago - 2 comments

#4 - Decide on how the setter should respond to invalid values

Issue - State: closed - Opened by domenic over 7 years ago - 3 comments

#4 - Decide on how the setter should respond to invalid values

Issue - State: closed - Opened by domenic over 7 years ago - 3 comments

#3 - Decide on what the default value is

Issue - State: closed - Opened by domenic over 7 years ago - 5 comments

#3 - Decide on what the default value is

Issue - State: closed - Opened by domenic over 7 years ago - 5 comments

#2 - Stratify the model into private variables and public getter/setter

Issue - State: closed - Opened by domenic over 7 years ago - 2 comments

#2 - Stratify the model into private variables and public getter/setter

Issue - State: closed - Opened by domenic over 7 years ago - 2 comments

#1 - Fix links to be to this repo instead of WICG

Issue - State: closed - Opened by domenic over 7 years ago

#1 - Fix links to be to this repo instead of WICG

Issue - State: closed - Opened by domenic over 7 years ago

GitHub / w3c/mst-content-hint issues and pull requests