Web Media API Community Group - Activity in 2017
No matches.
Participants
-
1 organization joined.
-
Condat AG joined.
-
GitHub
w3c-cg/webmediaapi
-
2 issues opened.
-
Broken fragment references to IndexedDB spec w3c-cg/webmediaapi#124, by @tidoust.
-
How should we specify WebGL in the spec? w3c-cg/webmediaapi#122, by @mavgit.
-
-
1 issue closed.
-
Broken fragment references to IndexedDB spec w3c-cg/webmediaapi#124.
-
-
2 issues received 6 new comments.
-
Broken fragment references to IndexedDB spec w3c-cg/webmediaapi#124 (3 comments by @davemevans, @johnluther, @mavgit)
-
How should we specify WebGL in the spec? w3c-cg/webmediaapi#122 (3 comments by @davemevans, @jpiesing, @wilaw)
-
-
3 pull requests opened.
-
Fix #122 - add a note encouraging WebGL implementation w3c-cg/webmediaapi#126, by @davemevans.
-
Fix #124 - Change IndexedDB reference to Version 1 rather than LATEST w3c-cg/webmediaapi#125, by @davemevans.
-
Fix issue #122 - remove WebGL w3c-cg/webmediaapi#123, by @davemevans.
-
-
2 pull requests merged.
-
Fix #124 - Change IndexedDB reference to Version 1 rather than LATEST w3c-cg/webmediaapi#125.
-
Fix #122 - add a note encouraging WebGL implementation w3c-cg/webmediaapi#126.
-
-
1 pull request closed.
-
Fix issue #122 - remove WebGL w3c-cg/webmediaapi#123.
-
-
3 pull requests received 3 new comments.
-
Fix #122 - add a note encouraging WebGL implementation w3c-cg/webmediaapi#126 (1 comment by @mavgit)
-
Fix #124 - Change IndexedDB reference to Version 1 rather than LATEST w3c-cg/webmediaapi#125 (1 comment by @mavgit)
-
GitHub
w3c-cg/webmediaapi
-
1 issue closed.
-
Editor's Note on WebDriver should be removed once test approach is clear w3c-cg/webmediaapi#118.
-
-
1 issue received 3 new comments.
-
Editor's Note on WebDriver should be removed once test approach is clear w3c-cg/webmediaapi#118 (3 comments by @davemevans, @mavgit)
-
-
2 pull requests opened.
-
Fix #118 - remove WebDriver API and associated editors note. w3c-cg/webmediaapi#121, by @davemevans.
-
Update editors note around Webdriver w3c-cg/webmediaapi#120, by @davemevans.
-
-
3 pull requests merged.
-
Various wordsmithing of non-normative sections w3c-cg/webmediaapi#119.
-
Fix #118 - remove WebDriver API and associated editors note. w3c-cg/webmediaapi#121.
-
Update editors note around Webdriver w3c-cg/webmediaapi#120.
-
-
1 pull request received 2 new comments.
GitHub
w3c-cg/webmediaapi
-
2 issues opened.
-
Editor's Note on WebDriver should be removed once test approach is clear w3c-cg/webmediaapi#118, by @davemevans.
-
Conformance testing of the Web Media API Snapshot spec w3c-cg/webmediaapi#116, by @andyburras.
-
-
4 issues closed.
-
Conformance testing of the Web Media API Snapshot spec w3c-cg/webmediaapi#116.
-
suggestion from IBC f2f w3c-cg/webmediaapi#113.
-
Title of Section 3.1.1 confusing in context of Section 3 w3c-cg/webmediaapi#114.
-
Add Geolocation API to list? w3c-cg/webmediaapi#110.
-
-
3 issues received 8 new comments.
-
Title of Section 3.1.1 confusing in context of Section 3 w3c-cg/webmediaapi#114 (3 comments by @davemevans, @mavgit)
-
Conformance testing of the Web Media API Snapshot spec w3c-cg/webmediaapi#116 (2 comments by @andyburras, @mavgit)
-
-
3 pull requests opened.
-
Various wordsmithing of non-normative sections w3c-cg/webmediaapi#119, by @davemevans.
-
Fix #113 - add text to make clear no removal of specs not included expected w3c-cg/webmediaapi#117, by @davemevans.
-
Fix #114 - change Section 3.1.1 title and tweak text w3c-cg/webmediaapi#115, by @davemevans.
-
-
2 pull requests merged.
-
Fix #113 - add text to make clear no removal of specs not included expected w3c-cg/webmediaapi#117.
-
Fix #114 - change Section 3.1.1 title and tweak text w3c-cg/webmediaapi#115.
-
-
1 pull request closed.
-
Fix #110 - add Geolocation API w3c-cg/webmediaapi#112.
-
-
2 pull requests received 2 new comments.
-
Fix #114 - change Section 3.1.1 title and tweak text w3c-cg/webmediaapi#115 (1 comment by @davemevans)
-
w3c-cg/webmediaporting
-
1 issue received 4 new comments.
Participants
-
2 organizations joined.
-
Eurofins Digital Testing joined.
-
Turner Broadcasting joined.
-
GitHub
w3c-cg/webmediaapi
-
4 issues opened.
-
Title of Section 3.1.1 confusing in context of Section 3 w3c-cg/webmediaapi#114, by @davemevans.
-
suggestion from IBC f2f w3c-cg/webmediaapi#113, by @jpiesing.
-
Add Geolocation API to list? w3c-cg/webmediaapi#110, by @mavgit.
-
Remove CORS spec based on recommendation from WebAppSec WG w3c-cg/webmediaapi#109, by @mavgit.
-
-
1 issue closed.
-
Remove CORS spec based on recommendation from WebAppSec WG w3c-cg/webmediaapi#109.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
Fix #110 - add Geolocation API w3c-cg/webmediaapi#112, by @davemevans.
-
Fix #109 - remove CORS based on WebAppSec recommendation w3c-cg/webmediaapi#111, by @davemevans.
-
-
1 pull request merged.
-
Fix #109 - remove CORS based on WebAppSec recommendation w3c-cg/webmediaapi#111.
-
-
2 pull requests received 2 new comments.
-
Fix #109 - remove CORS based on WebAppSec recommendation w3c-cg/webmediaapi#111 (1 comment by @davemevans)
w3c-cg/webmediaporting
-
3 issues opened.
-
Dual media element playback should be specified for ad insertion, etc. w3c-cg/webmediaporting#27, by @KilroyHughes.
-
abstract and introduction w3c-cg/webmediaporting#26, by @jpiesing.
-
how to organise the spec w3c-cg/webmediaporting#25, by @jpiesing.
-
-
1 issue closed.
-
how to organise the spec w3c-cg/webmediaporting#25.
-
-
5 issues received 10 new comments.
-
Dual media element playback should be specified for ad insertion, etc. w3c-cg/webmediaporting#27 (3 comments by @jpiesing, @KilroyHughes)
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaporting#9 (1 comment by @jpiesing)
Participants
-
1 participant joined.
-
seal chen joined.
-
GitHub
w3c-cg/webmediaporting
-
1 issue opened.
-
timing of generating the "ended" event w3c-cg/webmediaporting#24, by @jpiesing.
-
-
1 issue received 2 new comments.
-
proposal to change title of this spec to include "integration" w3c-cg/webmediaporting#1 (2 comments by @mavgit, @michelnev)
-
w3c-cg/webmediaapi
-
2 issues opened.
-
Use "lists" in place of "defines" since this specification does not define anything new w3c-cg/webmediaapi#106, by @davemevans.
-
Mark introductory sections as non-normative w3c-cg/webmediaapi#105, by @davemevans.
-
-
2 issues closed.
-
Mark introductory sections as non-normative w3c-cg/webmediaapi#105.
-
Use "lists" in place of "defines" since this specification does not define anything new w3c-cg/webmediaapi#106.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Mark introductory sections non-normative (see #105) w3c-cg/webmediaapi#108, by @davemevans.
-
Fix #106 - replace defines with lists w3c-cg/webmediaapi#107, by @davemevans.
-
-
2 pull requests merged.
-
Fix #106 - replace defines with lists w3c-cg/webmediaapi#107.
-
Mark introductory sections non-normative (see #105) w3c-cg/webmediaapi#108.
-
Reports
-
1 report published.
-
Web Media API Snapshot 2017 published as a final report.
-
GitHub
w3c-cg/webmediaapi
-
6 issues opened.
-
Support Content Security Policy spec w3c-cg/webmediaapi#104, by @mavgit.
-
Make EME conditional on CDM support w3c-cg/webmediaapi#103, by @mavgit.
-
Remove my email address w3c-cg/webmediaapi#98, by @mavgit.
-
Add boilerplate compliance section w3c-cg/webmediaapi#97, by @mavgit.
-
Update intro to section 3 to replace conformance sentence. w3c-cg/webmediaapi#95, by @mavgit.
-
Is "requiring" still appropriate now this is a snapshot? w3c-cg/webmediaapi#93, by @davemevans.
-
-
15 issues closed.
-
Support Content Security Policy spec w3c-cg/webmediaapi#104.
-
Make EME conditional on CDM support w3c-cg/webmediaapi#103.
-
Change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#70.
-
Add boilerplate compliance section w3c-cg/webmediaapi#97.
-
Remove my email address w3c-cg/webmediaapi#98.
-
Update intro to section 3 to replace conformance sentence. w3c-cg/webmediaapi#95.
-
Add WebDriver as Required spec to "Other web specifications" w3c-cg/webmediaapi#71.
-
Is "requiring" still appropriate now this is a snapshot? w3c-cg/webmediaapi#93.
-
Replace 'Recommended' with a synonym in Section 3 title w3c-cg/webmediaapi#84.
-
point out that future versions of the spec may drop APIs or parts of w3c-cg/webmediaapi#77.
-
Does our ISO Common Encryption reference need to be updated for CMAF? w3c-cg/webmediaapi#78.
-
Remove text around polyfills w3c-cg/webmediaapi#80.
-
Add a "Participate: File an issue (open issues)" section to the top of the spec w3c-cg/webmediaapi#87.
-
Change spec title to "Web Platform Snapshot 2017" w3c-cg/webmediaapi#88.
-
-
14 issues received 58 new comments.
-
Change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#70 (9 comments by @davemevans, @jpiesing, @mavgit)
-
Add WebDriver as Required spec to "Other web specifications" w3c-cg/webmediaapi#71 (9 comments by @davemevans, @jpiesing, @mavgit)
-
consider expanding the introduction with diagram from slides 7/8/9 of 2017-05-31 HATF phone conf w3c-cg/webmediaapi#72 (7 comments by @davemevans, @jpiesing, @mavgit)
-
Update intro to section 3 to replace conformance sentence. w3c-cg/webmediaapi#95 (6 comments by @davemevans, @jpiesing, @mavgit)
-
Change spec title to "Web Platform Snapshot 2017" w3c-cg/webmediaapi#88 (5 comments by @davemevans, @jpiesing, @mavgit)
-
Replace 'Recommended' with a synonym in Section 3 title w3c-cg/webmediaapi#84 (4 comments by @davemevans, @jpiesing, @mavgit)
-
Does our ISO Common Encryption reference need to be updated for CMAF? w3c-cg/webmediaapi#78 (4 comments by @jpiesing, @mavgit)
-
Add a "Participate: File an issue (open issues)" section to the top of the spec w3c-cg/webmediaapi#87 (3 comments by @davemevans, @mavgit)
-
point out that future versions of the spec may drop APIs or parts of w3c-cg/webmediaapi#77 (2 comments by @davemevans)
-
What additional web APIs need to be added to the draft Web Media API 2017 spec to support Progressive Web Apps? w3c-cg/webmediaapi#69 (2 comments by @davemevans, @mavgit)
-
Is "requiring" still appropriate now this is a snapshot? w3c-cg/webmediaapi#93 (1 comment by @mavgit)
-
-
10 pull requests opened.
-
Fix #70 - change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#102, by @davemevans.
-
Fix #95 - replace conformance sentence in proposed APIs section w3c-cg/webmediaapi#101, by @davemevans.
-
Fix #98 - remove mavs email address w3c-cg/webmediaapi#100, by @davemevans.
-
Fix #97 - add boilerplate compliance section w3c-cg/webmediaapi#99, by @davemevans.
-
Tweak wording around WebDriver at-risk note w3c-cg/webmediaapi#96, by @davemevans.
-
Add WebDriver, along with editors note that it is at-risk for now w3c-cg/webmediaapi#94, by @davemevans.
-
Remove Thasso from editors list w3c-cg/webmediaapi#92, by @davemevans.
-
Fix #84 - Replace Recommended with a synonym w3c-cg/webmediaapi#91, by @davemevans.
-
Change title to Web Media API Snapshot 2017 w3c-cg/webmediaapi#90, by @davemevans.
-
Fix #87 - add participate links w3c-cg/webmediaapi#89, by @davemevans.
-
-
14 pull requests merged.
-
Fix #70 - change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#102.
-
Tweak wording around WebDriver at-risk note w3c-cg/webmediaapi#96.
-
Fix #97 - add boilerplate compliance section w3c-cg/webmediaapi#99.
-
Fix #98 - remove mavs email address w3c-cg/webmediaapi#100.
-
Fix #95 - replace conformance sentence in proposed APIs section w3c-cg/webmediaapi#101.
-
Add WebDriver, along with editors note that it is at-risk for now w3c-cg/webmediaapi#94.
-
Remove Thasso from editors list w3c-cg/webmediaapi#92.
-
Fix #84 - Replace Recommended with a synonym w3c-cg/webmediaapi#91.
-
First stab at a proper introduction w3c-cg/webmediaapi#86.
-
Implement #78 - remove note about CENC update w3c-cg/webmediaapi#82.
-
Implements decision in #80 to remove incorrect text about polyfills w3c-cg/webmediaapi#83.
-
Implement #69: Include APIs required and recommended for PWA support w3c-cg/webmediaapi#85.
-
Fix #87 - add participate links w3c-cg/webmediaapi#89.
-
Change title to Web Media API Snapshot 2017 w3c-cg/webmediaapi#90.
-
-
10 pull requests received 17 new comments.
-
Add WebDriver, along with editors note that it is at-risk for now w3c-cg/webmediaapi#94 (7 comments by @davemevans, @jpiesing, @mavgit)
-
Fix #70 - change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#102 (1 comment by @mavgit)
-
Implements decision in #80 to remove incorrect text about polyfills w3c-cg/webmediaapi#83 (1 comment by @mavgit)
-
Implement #69: Include APIs required and recommended for PWA support w3c-cg/webmediaapi#85 (1 comment by @mavgit)
-
w3c-cg/webmediaporting
-
1 issue received 1 new comment.
-
proposal to change title of this spec to include "integration" w3c-cg/webmediaporting#1 (1 comment by @michelnev)
-
GitHub
w3c-cg/webmediaapi
-
8 issues opened.
-
Change spec title to "Web Platform Snapshot 2017" w3c-cg/webmediaapi#88, by @mavgit.
-
Add a "Participate: File an issue (open issues)" section to the top of the spec w3c-cg/webmediaapi#87, by @mavgit.
-
Replace 'Recommended' with a synonym in Section 3 title w3c-cg/webmediaapi#84, by @davemevans.
-
Remove text around polyfills w3c-cg/webmediaapi#80, by @davemevans.
-
Does our ISO Common Encryption reference need to be updated for CMAF? w3c-cg/webmediaapi#78, by @davemevans.
-
point out that future versions of the spec may drop APIs or parts of w3c-cg/webmediaapi#77, by @jpiesing.
-
Test issue - please ignore w3c-cg/webmediaapi#73, by @mavgit.
-
consider expanding the introduction with diagram from slides 7/8/9 of 2017-05-31 HATF phone conf w3c-cg/webmediaapi#72, by @jpiesing.
-
-
21 issues closed.
-
Review new TAG Finding on "The evergreen Web" w3c-cg/webmediaapi#39.
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaapi#55.
-
Minimum graphics performance w3c-cg/webmediaapi#54.
-
Application loading & transition times w3c-cg/webmediaapi#53.
-
formatting of HTTP user agent string w3c-cg/webmediaapi#52.
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaapi#50.
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaapi#49.
-
requirements on graphics resolution for rendering browser UI w3c-cg/webmediaapi#48.
-
requirements on URL length w3c-cg/webmediaapi#47.
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaapi#46.
-
root certificates for TLS w3c-cg/webmediaapi#45.
-
launching first page of web app in full screen mode w3c-cg/webmediaapi#44.
-
requirements on MSE buffering and timing w3c-cg/webmediaapi#43.
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaapi#42.
-
Missing key content in Web Media Document w3c-cg/webmediaapi#30.
-
Explicitly require cookies? w3c-cg/webmediaapi#9.
-
Test issue - please ignore w3c-cg/webmediaapi#73.
-
Web specifications used by HbbTV and not in Web Media API spec w3c-cg/webmediaapi#19.
-
Web Messaging w3c-cg/webmediaapi#15.
-
objection to PR #62 as implemented after 05/04/17 call w3c-cg/webmediaapi#67.
-
-
29 issues received 70 new comments.
-
Change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#70 (7 comments by @davemevans, @jpiesing, @mavgit)
-
Add WebDriver as Required spec to "Other web specifications" w3c-cg/webmediaapi#71 (6 comments by @davemevans, @jpiesing, @mavgit)
-
What additional web APIs need to be added to the draft Web Media API 2017 spec to support Progressive Web Apps? w3c-cg/webmediaapi#69 (6 comments by @davemevans, @hober, @mavgit, @tidoust)
-
point out that future versions of the spec may drop APIs or parts of w3c-cg/webmediaapi#77 (4 comments by @davemevans, @mavgit)
-
Test issue - please ignore w3c-cg/webmediaapi#73 (4 comments by @davemevans, @joelkorpi, @mavgit, @ZmGorynych)
-
Replace 'Recommended' with a synonym in Section 3 title w3c-cg/webmediaapi#84 (3 comments by @jpiesing, @mavgit)
-
Does our ISO Common Encryption reference need to be updated for CMAF? w3c-cg/webmediaapi#78 (3 comments by @davemevans, @jpiesing)
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaapi#55 (3 comments by @mavgit, @michelnev, @NevBosak)
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaapi#42 (3 comments by @IDWMaster, @jpiesing, @mavgit)
-
consider expanding the introduction with diagram from slides 7/8/9 of 2017-05-31 HATF phone conf w3c-cg/webmediaapi#72 (2 comments by @davemevans, @mavgit)
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaapi#46 (2 comments by @mavgit, @michelnev)
-
launching first page of web app in full screen mode w3c-cg/webmediaapi#44 (2 comments by @mavgit, @michelnev)
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaapi#50 (1 comment by @mavgit)
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaapi#49 (1 comment by @mavgit)
-
requirements on graphics resolution for rendering browser UI w3c-cg/webmediaapi#48 (1 comment by @mavgit)
-
is requiring support for 100% accurate video seeking reasonable with hardware video decoders? w3c-cg/webmediaapi#28 (1 comment by @mavgit)
-
Web specifications used by HbbTV and not in Web Media API spec w3c-cg/webmediaapi#19 (1 comment by @davemevans)
-
objection to PR #62 as implemented after 05/04/17 call w3c-cg/webmediaapi#67 (1 comment by @davemevans)
-
-
9 pull requests opened.
-
First stab at a proper introduction w3c-cg/webmediaapi#86, by @davemevans.
-
Implement #69: Include APIs required and recommended for PWA support w3c-cg/webmediaapi#85, by @davemevans.
-
Implements decision in #80 to remove incorrect text about polyfills w3c-cg/webmediaapi#83, by @davemevans.
-
Implement #78 - remove note about CENC update w3c-cg/webmediaapi#82, by @davemevans.
-
Fix ReSpec issues w3c-cg/webmediaapi#81, by @davemevans.
-
[Editorial] list authors alphabetically w3c-cg/webmediaapi#79, by @davemevans.
-
Refactor recommended specifications into separate section etc. w3c-cg/webmediaapi#76, by @davemevans.
-
Fix #15 - add undated refs to WHATWG HTML for channel- and web-messaging w3c-cg/webmediaapi#75, by @davemevans.
-
Fix #67 - update statement on unimplemented features w3c-cg/webmediaapi#74, by @davemevans.
-
-
6 pull requests merged.
-
Fix ReSpec issues w3c-cg/webmediaapi#81.
-
[Editorial] list authors alphabetically w3c-cg/webmediaapi#79.
-
Refactor recommended specifications into separate section etc. w3c-cg/webmediaapi#76.
-
Fix #15 - add undated refs to WHATWG HTML for channel- and web-messaging w3c-cg/webmediaapi#75.
-
Fix #67 - update statement on unimplemented features w3c-cg/webmediaapi#74.
-
addition of link to web developer guidelines w3c-cg/webmediaapi#64.
-
-
1 pull request closed.
-
Require cookies, including a mandatory minimum capability w3c-cg/webmediaapi#31.
-
-
5 pull requests received 12 new comments.
-
Refactor recommended specifications into separate section etc. w3c-cg/webmediaapi#76 (8 comments by @davemevans, @mavgit)
-
Require cookies, including a mandatory minimum capability w3c-cg/webmediaapi#31 (1 comment by @davemevans)
-
w3c-cg/webmediaporting
-
19 issues opened.
-
what devices are targeted by this spec? w3c-cg/webmediaporting#23, by @jpiesing.
-
Add something about key codes w3c-cg/webmediaporting#22, by @davemevans.
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaporting#21, by @mavgit.
-
Minimum graphics performance w3c-cg/webmediaporting#20, by @mavgit.
-
Application loading & transition times w3c-cg/webmediaporting#19, by @mavgit.
-
formatting of HTTP user agent string w3c-cg/webmediaporting#18, by @mavgit.
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaporting#17, by @mavgit.
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaporting#16, by @mavgit.
-
requirements on graphics resolution for rendering browser UI w3c-cg/webmediaporting#15, by @mavgit.
-
requirements on URL length w3c-cg/webmediaporting#14, by @mavgit.
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaporting#13, by @mavgit.
-
root certificates for TLS w3c-cg/webmediaporting#12, by @mavgit.
-
launching first page of web app in full screen mode w3c-cg/webmediaporting#11, by @mavgit.
-
requirements on MSE buffering and timing w3c-cg/webmediaporting#10, by @mavgit.
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaporting#9, by @mavgit.
-
Missing key content in Web Media Document w3c-cg/webmediaporting#8, by @mavgit.
-
is requiring support for 100% accurate video seeking reasonable with hardware video decoders? w3c-cg/webmediaporting#7, by @mavgit.
-
Explicitly require cookies? w3c-cg/webmediaporting#6, by @mavgit.
-
Test issue - please ignore w3c-cg/webmediaporting#5, by @mavgit.
-
-
1 issue closed.
-
Test issue - please ignore w3c-cg/webmediaporting#5.
-
-
19 issues received 83 new comments.
-
launching first page of web app in full screen mode w3c-cg/webmediaporting#11 (12 comments by @mavgit)
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaporting#21 (5 comments by @mavgit)
-
proposal to change title of this spec to include "integration" w3c-cg/webmediaporting#1 (4 comments by @jpiesing, @mavgit, @michelnev)
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaporting#9 (3 comments by @mavgit)
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaporting#16 (2 comments by @mavgit)
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaporting#13 (2 comments by @mavgit)
-
fullscreen api: is a request to fullscreen a video element guaranteed to succeed? w3c-cg/webmediaporting#4 (2 comments by @jpiesing, @michelnev)
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaporting#17 (1 comment by @mavgit)
-
is requiring support for 100% accurate video seeking reasonable with hardware video decoders? w3c-cg/webmediaporting#7 (1 comment by @mavgit)
GitHub
w3c-cg/webmediaporting
-
4 issues opened.
-
fullscreen api: is a request to fullscreen a video element guaranteed to succeed? w3c-cg/webmediaporting#4, by @jpiesing.
-
fullscreen api: implementations without any browser chrome w3c-cg/webmediaporting#3, by @jpiesing.
-
Information on Cobalt w3c-cg/webmediaporting#2, by @hbengali.
-
proposal to change title of this spec to include "integration" w3c-cg/webmediaporting#1, by @jpiesing.
-
w3c-cg/webmediaapi
-
2 issues opened.
-
Add WebDriver as Required spec to "Other web specifications" w3c-cg/webmediaapi#71, by @mavgit.
-
Change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#70, by @davemevans.
-
-
6 issues closed.
-
what does it mean to support the fullscreen API on a TV? w3c-cg/webmediaapi#22.
-
Which HTML UA code bases need to support Web Media APIs? w3c-cg/webmediaapi#27.
-
Specify conformance class when needed, for HTML5.1 in particular w3c-cg/webmediaapi#21.
-
Clarify needs for DOM specifications section w3c-cg/webmediaapi#3.
-
Clarify which version of XHR is required w3c-cg/webmediaapi#1.
-
Websocket protocol - RFC6455 w3c-cg/webmediaapi#16.
-
-
20 issues received 61 new comments.
-
what does it mean to support the fullscreen API on a TV? w3c-cg/webmediaapi#22 (15 comments by @davemevans, @jpiesing, @mavgit)
-
launching first page of web app in full screen mode w3c-cg/webmediaapi#44 (10 comments by @davemevans, @jpiesing, @mavgit)
-
What additional web APIs need to be added to the draft Web Media API 2017 spec to support Progressive Web Apps? w3c-cg/webmediaapi#69 (6 comments by @davemevans, @hbengali, @hober, @jpiesing, @mavgit)
-
Add WebDriver as Required spec to "Other web specifications" w3c-cg/webmediaapi#71 (4 comments by @jpiesing, @mavgit)
-
objection to PR #62 as implemented after 05/04/17 call w3c-cg/webmediaapi#67 (3 comments by @davemevans, @jpiesing, @mavgit)
-
requirements on MSE buffering and timing w3c-cg/webmediaapi#43 (3 comments by @davemevans, @jpiesing)
-
Change opening statement around code base support of APIs at publication time w3c-cg/webmediaapi#70 (3 comments by @jpiesing, @mavgit)
-
Which HTML UA code bases need to support Web Media APIs? w3c-cg/webmediaapi#27 (2 comments by @davemevans)
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaapi#55 (1 comment by @mavgit)
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaapi#50 (1 comment by @jpiesing)
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaapi#46 (1 comment by @jpiesing)
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaapi#42 (1 comment by @jpiesing)
-
Specify conformance class when needed, for HTML5.1 in particular w3c-cg/webmediaapi#21 (1 comment by @davemevans)
-
-
4 pull requests merged.
-
Issue #27 - add text about polyfills, UA version numbers w3c-cg/webmediaapi#65.
-
Issue #21 - add conformance class for HTML 5.1 w3c-cg/webmediaapi#66.
-
Issue #3 - replace DOM Reqs (Section 2.2) with note similar to description in issue. w3c-cg/webmediaapi#68.
-
Fix #1: Don't specify Level 1 for XHR support. w3c-cg/webmediaapi#8.
-
GitHub
w3c-cg/webmediaapi
-
3 issues opened.
-
objection to PR #62 as implemented after 05/04/17 call w3c-cg/webmediaapi#67, by @jpiesing.
-
5 issues closed.
-
HbbTV spec made some parts of CSS Basic User Interface optional w3c-cg/webmediaapi#24.
-
general issue of features that are 'at risk' w3c-cg/webmediaapi#25.
-
subsetting workers w3c-cg/webmediaapi#23.
-
Fetch w3c-cg/webmediaapi#60.
-
Media Fragments URI w3c-cg/webmediaapi#14.
-
-
19 issues received 42 new comments.
-
formatting of HTTP user agent string w3c-cg/webmediaapi#52 (8 comments by @jeremypoulter, @joelkorpi, @joeyparrish, @jpiesing, @mavgit)
-
Clarify which version of XHR is required w3c-cg/webmediaapi#1 (5 comments by @davemevans, @joeyparrish, @mavgit)
-
Which HTML UA code bases need to support Web Media APIs? w3c-cg/webmediaapi#27 (4 comments by @davemevans, @mavgit)
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaapi#55 (2 comments by @jpiesing, @mavgit)
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaapi#49 (2 comments by @davemevans, @jpiesing)
-
what does it mean to support the fullscreen API on a TV? w3c-cg/webmediaapi#22 (2 comments by @davemevans, @mavgit)
-
Specify conformance class when needed, for HTML5.1 in particular w3c-cg/webmediaapi#21 (2 comments by @davemevans)
-
launching first page of web app in full screen mode w3c-cg/webmediaapi#44 (1 comment by @davemevans)
-
What additional web APIs need to be added to the draft Web Media API 2017 spec to support Progressive Web Apps? w3c-cg/webmediaapi#69 (1 comment by @davemevans)
-
HbbTV spec made some parts of CSS Basic User Interface optional w3c-cg/webmediaapi#24 (1 comment by @davemevans)
-
-
7 pull requests opened.
-
Issue #3 - replace DOM Reqs (Section 2.2) with note similar to description in issue. w3c-cg/webmediaapi#68, by @davemevans.
-
Issue #21 - add conformance class for HTML 5.1 w3c-cg/webmediaapi#66, by @davemevans.
-
Issue #27 - add text about polyfills, UA version numbers w3c-cg/webmediaapi#65, by @davemevans.
-
addition of link to web developer guidelines w3c-cg/webmediaapi#64, by @boyofgreen.
-
Fix #60 - Require Fetch w3c-cg/webmediaapi#63, by @davemevans.
-
Create section noting exceptions from testing w3c-cg/webmediaapi#62, by @davemevans.
-
Require Media Fragments URI w3c-cg/webmediaapi#61, by @davemevans.
-
-
4 pull requests merged.
-
Create section noting exceptions from testing w3c-cg/webmediaapi#62.
-
Fix #60 - Require Fetch w3c-cg/webmediaapi#63.
-
[Editorial] Change another 'support' to 'be conforming implementations of' w3c-cg/webmediaapi#59.
-
Require Media Fragments URI w3c-cg/webmediaapi#61.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants joined.
-
Alexandre Nicastro joined.
-
JARBAS MENEZES joined.
-
-
1 participant left.
-
Alexandre Nicastro left.
-
-
3 organizations joined.
-
JW Player joined.
-
uStudio, Inc joined.
-
LongTail Video joined.
-
-
2 organizations left.
-
LongTail Video left.
-
LongTail Video left.
-
GitHub
w3c-cg/webmediaapi
-
14 issues opened.
-
requirements from web video providers beyond presence or absence of an API w3c-cg/webmediaapi#55, by @jpiesing.
-
Minimum graphics performance w3c-cg/webmediaapi#54, by @jpiesing.
-
Application loading & transition times w3c-cg/webmediaapi#53, by @jpiesing.
-
formatting of HTTP user agent string w3c-cg/webmediaapi#52, by @jpiesing.
-
Use of 'support' w3c-cg/webmediaapi#51, by @jeremypoulter.
-
minimum requirements on devices being able to generate certain key events w3c-cg/webmediaapi#50, by @jpiesing.
-
relationship of graphics resolution and coordinate spaces to video resolution / coordinates w3c-cg/webmediaapi#49, by @jpiesing.
-
requirements on graphics resolution for rendering browser UI w3c-cg/webmediaapi#48, by @jpiesing.
-
requirements on URL length w3c-cg/webmediaapi#47, by @jpiesing.
-
requirements on number of simultaneous HTTP connections w3c-cg/webmediaapi#46, by @jpiesing.
-
root certificates for TLS w3c-cg/webmediaapi#45, by @jpiesing.
-
launching first page of web app in full screen mode w3c-cg/webmediaapi#44, by @jpiesing.
-
requirements on MSE buffering and timing w3c-cg/webmediaapi#43, by @jpiesing.
-
accuracy of reporting the current playback position for the media element w3c-cg/webmediaapi#42, by @jpiesing.
-
-
9 issues closed.
-
Use of 'support' w3c-cg/webmediaapi#51.
-
APIs for offline playback w3c-cg/webmediaapi#26.
-
CSSOM View Module w3c-cg/webmediaapi#12.
-
DOM level 3 events w3c-cg/webmediaapi#13.
-
CSS Text Module Level 3 w3c-cg/webmediaapi#11.
-
Check CSS Snapshot 2017 w3c-cg/webmediaapi#34.
-
Which version of ECMAScript should be referenced? w3c-cg/webmediaapi#20.
-
WebAudio w3c-cg/webmediaapi#18.
-
Add IndexedDB in "Other web specifications"? w3c-cg/webmediaapi#4.
-
-
19 issues received 64 new comments.
-
APIs for offline playback w3c-cg/webmediaapi#26 (9 comments by @davemevans, @joeyparrish, @jpiesing, @tidoust)
-
Which HTML UA code bases need to support Web Media APIs? w3c-cg/webmediaapi#27 (9 comments by @davemevans, @jeremypoulter, @jpiesing, @mavgit)
-
formatting of HTTP user agent string w3c-cg/webmediaapi#52 (6 comments by @davemevans, @jeremypoulter, @jpiesing, @tidoust)
-
Add IndexedDB in "Other web specifications"? w3c-cg/webmediaapi#4 (5 comments by @davemevans, @joeyparrish, @mavgit, @thasso)
-
what does it mean to support the fullscreen API on a TV? w3c-cg/webmediaapi#22 (2 comments by @davemevans)
-
Specify conformance class when needed, for HTML5.1 in particular w3c-cg/webmediaapi#21 (2 comments by @mavgit, @tidoust)
-
Web specifications used by HbbTV and not in Web Media API spec w3c-cg/webmediaapi#19 (1 comment by @mavgit)
-
-
6 pull requests opened.
-
[Editorial] Change another 'support' to 'be conforming implementations of' w3c-cg/webmediaapi#59, by @davemevans.
-
Fix for Issue #51 - Replace 'support' with 'be conforming implementat… w3c-cg/webmediaapi#58, by @thasso.
-
Fix #34 - CSS Snapshot to 2017 w3c-cg/webmediaapi#57, by @thasso.
-
Fix #20 - ECMAScript Reference w3c-cg/webmediaapi#56, by @thasso.
-
Fix #18 - Require Web Audio API w3c-cg/webmediaapi#41, by @davemevans.
-
Fix #4 - Require support for IndexedDB w3c-cg/webmediaapi#40, by @davemevans.
-
-
5 pull requests merged.
-
Fix for Issue #51 - Replace 'support' with 'be conforming implementat… w3c-cg/webmediaapi#58.
-
Fix #34 - CSS Snapshot to 2017 w3c-cg/webmediaapi#57.
-
Fix #20 - ECMAScript Reference w3c-cg/webmediaapi#56.
-
Fix #18 - Require Web Audio API w3c-cg/webmediaapi#41.
-
Fix #4 - Require support for IndexedDB w3c-cg/webmediaapi#40.
-
-
1 pull request received 1 new comment.
-
Fix for Issue #51 - Replace 'support' with 'be conforming implementat… w3c-cg/webmediaapi#58 (1 comment by @davemevans)
-
Participants
-
1 organization joined.
-
Castlabs GmbH joined.
-
GitHub
w3c-cg/webmediaapi
-
2 issues opened.
-
Review new TAG Finding on "The evergreen Web" w3c-cg/webmediaapi#39, by @tidoust.
-
Check CSS Snapshot 2017 w3c-cg/webmediaapi#34, by @tidoust.
-
-
3 issues closed.
-
Require GIF graphics format w3c-cg/webmediaapi#2.
-
Support Server-Sent Events/EventSource w3c-cg/webmediaapi#6.
-
Server-sent events w3c-cg/webmediaapi#17.
-
-
15 issues received 47 new comments.
-
what does it mean to support the fullscreen API on a TV? w3c-cg/webmediaapi#22 (5 comments by @jpiesing, @mavgit, @thasso)
-
Which version of ECMAScript should be referenced? w3c-cg/webmediaapi#20 (4 comments by @davemevans, @jpiesing, @mavgit)
-
Explicitly require cookies? w3c-cg/webmediaapi#9 (4 comments by @boyofgreen, @davemevans, @jpiesing, @wfoote)
-
Add IndexedDB in "Other web specifications"? w3c-cg/webmediaapi#4 (4 comments by @davemevans, @jpiesing, @tidoust)
-
is requiring support for 100% accurate video seeking reasonable with hardware video decoders? w3c-cg/webmediaapi#28 (1 comment by @thasso)
-
7 pull requests opened.
-
Re-add Replace editors note with issue about ES version w3c-cg/webmediaapi#38, by @davemevans.
-
Optionally require web workers w3c-cg/webmediaapi#37, by @davemevans.
-
Replace editors note with issue about ES version w3c-cg/webmediaapi#36, by @davemevans.
-
Added Thasso Griebel to the editor list w3c-cg/webmediaapi#35, by @thasso.
-
[Editorial] Fix some HTML errors w3c-cg/webmediaapi#33, by @davemevans.
-
Add David Evans (BBC) as editor w3c-cg/webmediaapi#32, by @davemevans.
-
Require cookies, including a mandatory minimum capability w3c-cg/webmediaapi#31, by @davemevans.
-
-
7 pull requests merged.
-
Re-add Replace editors note with issue about ES version w3c-cg/webmediaapi#38.
-
Fix #2: Add GIF89a to required graphics specifications w3c-cg/webmediaapi#5.
-
Fix #6 - recommend Server-Sent Event support w3c-cg/webmediaapi#29.
-
Add David Evans (BBC) as editor w3c-cg/webmediaapi#32.
-
[Editorial] Fix some HTML errors w3c-cg/webmediaapi#33.
-
Added Thasso Griebel to the editor list w3c-cg/webmediaapi#35.
-
Replace editors note with issue about ES version w3c-cg/webmediaapi#36.
-
-
1 pull request closed.
-
Optionally require web workers w3c-cg/webmediaapi#37.
-
-
3 pull requests received 3 new comments.
Participants
-
2 organizations joined.
-
Microsoft Corporation joined.
-
Digital TV Labs Ltd joined.
-
GitHub
w3c-cg/webmediaapi
-
1 issue opened.
-
Missing key content in Web Media Document w3c-cg/webmediaapi#30, by @boyofgreen.
-
-
4 issues received 4 new comments.
-
Which HTML UA code bases need to support Web Media APIs? w3c-cg/webmediaapi#27 (1 comment by @boyofgreen)
-