Second Screen Working Group - Activity in 2017
No matches.
GitHub
w3c/presentation-api
-
1 issue received 1 new comment.
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444 (1 comment by @schien)
-
w3c/remote-playback
-
1 issue closed.
-
1 issue received 1 new comment.
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (1 comment by @anssiko)
-
-
1 pull request opened.
-
Addresses Issue 41 w3c/remote-playback#112, by @markafoltz.
-
-
1 pull request merged.
-
Addresses Issue 41 w3c/remote-playback#112.
-
-
1 pull request received 2 new comments.
GitHub
w3c/secondscreen-charter
-
5 issues opened.
-
Presentation/Remote Playback API Testing API w3c/secondscreen-charter#6, by @markafoltz.
-
Presentation API Level 2 w3c/secondscreen-charter#5, by @markafoltz.
-
Remote Playback API w3c/secondscreen-charter#4, by @markafoltz.
-
Presentation API w3c/secondscreen-charter#3, by @markafoltz.
-
Adopt test as you commit policy? w3c/secondscreen-charter#2, by @anssiko.
-
-
5 issues closed.
-
Adopt test as you commit policy? w3c/secondscreen-charter#2.
-
Presentation API w3c/secondscreen-charter#3.
-
Remote Playback API w3c/secondscreen-charter#4.
-
Presentation API Level 2 w3c/secondscreen-charter#5.
-
Presentation/Remote Playback API Testing API w3c/secondscreen-charter#6.
-
-
4 issues received 6 new comments.
-
Adopt test as you commit policy? w3c/secondscreen-charter#2 (3 comments by @anssiko, @markafoltz, @tidoust)
-
-
2 pull requests opened.
-
Addresses Issues #3-#6 w3c/secondscreen-charter#7, by @markafoltz.
-
Update charter based on F2F discussions during TPAC w3c/secondscreen-charter#1, by @tidoust.
-
-
1 pull request merged.
-
Update charter based on F2F discussions during TPAC w3c/secondscreen-charter#1.
-
-
1 pull request closed.
-
Addresses Issues #3-#6 w3c/secondscreen-charter#7.
-
-
2 pull requests received 18 new comments.
-
Update charter based on F2F discussions during TPAC w3c/secondscreen-charter#1 (13 comments by @anssiko, @markafoltz, @tidoust)
-
w3c/presentation-api
-
9 issues received 21 new comments.
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444 (4 comments by @anssiko, @louaybassbouss, @markafoltz, @toji)
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (4 comments by @anssiko, @markafoltz)
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67 (3 comments by @chrisn, @markafoltz)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (2 comments by @anssiko, @markafoltz)
-
Presentation display capability detection w3c/presentation-api#348 (2 comments by @anssiko, @markafoltz)
-
-
1 pull request opened.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/presentation-api#445, by @foolip.
-
-
1 pull request merged.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/presentation-api#445.
-
-
1 pull request received 1 new comment.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/presentation-api#445 (1 comment by @markafoltz)
-
w3c/openscreenprotocol
-
7 issues opened.
-
[QUIC] Investigate and propose use of DataChannel framing on top of QUIC w3c/openscreenprotocol#84, by @markafoltz.
-
[DataChannel] Investigate use of DataChannel without all of WebRTC w3c/openscreenprotocol#83, by @markafoltz.
-
[QUIC] Find out timeline for TLS 1.3 and QUIC v1 w3c/openscreenprotocol#82, by @markafoltz.
-
[SSDP] Update implementation information w3c/openscreenprotocol#81, by @markafoltz.
-
Investigate message latency requirements for media sync w3c/openscreenprotocol#80, by @markafoltz.
-
Clarify hardware requirements w3c/openscreenprotocol#79, by @markafoltz.
-
[Protocol] Hand-rolled binary protocol? w3c/openscreenprotocol#77, by @cynthia.
-
-
7 issues received 19 new comments.
-
[QUIC] Investigate WebSocket layering onto QUIC w3c/openscreenprotocol#62 (11 comments by @louaybassbouss, @markafoltz, @schien, @tomoyukilabs)
-
[QUIC] Investigate and propose use of DataChannel framing on top of QUIC w3c/openscreenprotocol#84 (2 comments by @markafoltz, @schien)
-
[Meta] Propose security mechanisms for Open Screen protocol w3c/openscreenprotocol#13 (2 comments by @anssiko, @markafoltz)
-
[Meta] Performance data for discovery protocols w3c/openscreenprotocol#69 (1 comment by @markafoltz)
-
Investigate message latency requirements for media sync w3c/openscreenprotocol#80 (1 comment by @markafoltz)
-
[DataChannel] Define bootstrap mechanism for QUIC (or RTCDataChannel) w3c/openscreenprotocol#73 (1 comment by @schien)
-
-
1 pull request opened.
-
Fix links to issues w3c/openscreenprotocol#78, by @anssiko.
-
-
1 pull request merged.
-
Fix links to issues w3c/openscreenprotocol#78.
-
-
1 pull request reopened.
-
Fix links to issues w3c/openscreenprotocol#78, by @markafoltz.
-
-
1 pull request received 2 new comments.
w3c/remote-playback
-
1 issue closed.
-
Remote playback device capabilities not always a subset of local playback device's w3c/remote-playback#88.
-
-
4 issues received 8 new comments.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (5 comments by @Honry, @louaybassbouss, @markafoltz, @mounirlamouri)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (1 comment by @markafoltz)
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46 (1 comment by @mounirlamouri)
-
Remote playback device capabilities not always a subset of local playback device's w3c/remote-playback#88 (1 comment by @mounirlamouri)
-
TR publications
-
1 document published.
-
Remote Playback API published as a Candidate Recommendation Snapshot. History of Remote Playback API
-
Participants
-
1 organization joined.
-
Dong-Eui University joined.
-
GitHub
w3c/presentation-api
-
1 issue opened.
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444, by @markafoltz.
-
-
3 issues received 11 new comments.
-
Presentation Testing API w3c/presentation-api#440 (7 comments by @anssiko, @louaybassbouss, @markafoltz, @tomoyukilabs)
-
Consider use cases for Presentation API v2 with VR capable displays w3c/presentation-api#444 (3 comments by @anssiko, @louaybassbouss, @toji)
-
-
3 pull requests opened.
-
Update Blob reference w3c/presentation-api#443, by @anssiko.
-
Fix ReSpec console warnings w3c/presentation-api#442, by @anssiko.
-
Fix ReSpec warnings w3c/presentation-api#441, by @anssiko.
-
-
3 pull requests merged.
-
Update Blob reference w3c/presentation-api#443.
-
Fix ReSpec console warnings w3c/presentation-api#442.
-
Fix ReSpec warnings w3c/presentation-api#441.
-
-
1 pull request received 2 new comments.
w3c/remote-playback
-
1 issue opened.
-
Rephrase normative statement in security and privacy consideration section w3c/remote-playback#109, by @tidoust.
-
-
3 issues closed.
-
[meta] Publish Candidate Recommendation w3c/remote-playback#73.
-
Restrict the API to Secure Contexts or discuss the decision in Security Considerations w3c/remote-playback#107.
-
Rephrase normative statement in security and privacy consideration section w3c/remote-playback#109.
-
-
5 issues received 15 new comments.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (8 comments by @anssiko, @Honry, @louaybassbouss, @markafoltz)
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46 (1 comment by @anssiko)
-
Remote playback device capabilities not always a subset of local playback device's w3c/remote-playback#88 (1 comment by @anssiko)
-
Rephrase normative statement in security and privacy consideration section w3c/remote-playback#109 (1 comment by @markafoltz)
-
-
3 pull requests opened.
-
Fix broken reference to "Monitoring" algorithm w3c/remote-playback#111, by @tidoust.
-
'Potentially secure' is now 'potentially trustworthy origin' w3c/remote-playback#110, by @anssiko.
-
Mention behaviour on Secure Contexts (fixes 107). w3c/remote-playback#108, by @mounirlamouri.
-
-
3 pull requests merged.
-
Fix broken reference to "Monitoring" algorithm w3c/remote-playback#111.
-
'Potentially secure' is now 'potentially trustworthy origin' w3c/remote-playback#110.
-
Mention behaviour on Secure Contexts (fixes 107). w3c/remote-playback#108.
-
-
1 pull request received 10 new comments.
-
Mention behaviour on Secure Contexts (fixes 107). w3c/remote-playback#108 (10 comments by @anssiko, @markafoltz, @mounirlamouri, @tidoust)
-
w3c/openscreenprotocol
-
13 issues opened.
-
[meta] Performance data for transport protocols w3c/openscreenprotocol#74, by @markafoltz.
-
[DataChannel] Define bootstrap mechanism for QUIC (or RTCDataChannel) w3c/openscreenprotocol#73, by @markafoltz.
-
Investigate measurement techniques for network power consumption on mobile devices w3c/openscreenprotocol#72, by @markafoltz.
-
[Meta] Performance data for discovery protocols w3c/openscreenprotocol#69, by @markafoltz.
-
[SSDP] Get reliability data w3c/openscreenprotocol#68, by @markafoltz.
-
[QUIC] Get data on connection and message latency w3c/openscreenprotocol#66, by @markafoltz.
-
[QUIC] Get data on network and power efficiency w3c/openscreenprotocol#65, by @markafoltz.
-
[QUIC] Get hardware requirements w3c/openscreenprotocol#64, by @markafoltz.
-
[QUIC] Get reliability data w3c/openscreenprotocol#63, by @markafoltz.
-
[QUIC] Investigate WebSocket layering onto QUIC w3c/openscreenprotocol#62, by @markafoltz.
-
[Control] Bidirectional control protocol w3c/openscreenprotocol#61, by @markafoltz.
-
[Editorial] Use compact and readable syntax for protocol messages w3c/openscreenprotocol#60, by @markafoltz.
-
[SSDP] Update proposed use of SSDP to specifically prevent SSDP amplification attacks w3c/openscreenprotocol#57, by @markafoltz.
-
-
3 issues closed.
-
[SSDP] Investigate licensing requirements for uPnP w3c/openscreenprotocol#27.
-
[SSDP] Research history of uPnP exploits w3c/openscreenprotocol#25.
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5.
-
-
6 issues received 7 new comments.
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (2 comments by @chrisn, @markafoltz)
-
[DataChannel] Define bootstrap mechanism for QUIC (or RTCDataChannel) w3c/openscreenprotocol#73 (1 comment by @schien)
-
[Meta] Performance data for discovery protocols w3c/openscreenprotocol#69 (1 comment by @louaybassbouss)
-
[SSDP] Investigate mechanisms to pre-filter devices by Presentation URL w3c/openscreenprotocol#21 (1 comment by @markafoltz)
-
[SSDP] Ensure that advertised friendly names are i18n capable w3c/openscreenprotocol#22 (1 comment by @markafoltz)
-
-
8 pull requests opened.
-
Add Chrome OS to platform support w3c/openscreenprotocol#76, by @beaufortfrancois.
-
Adds transport benchmark design w3c/openscreenprotocol#75, by @markafoltz.
-
Benchmark design for discovery protocols. w3c/openscreenprotocol#71, by @markafoltz.
-
Updates links to issues relating to performance data for discovery. w3c/openscreenprotocol#70, by @markafoltz.
-
Updates QUIC proposal. w3c/openscreenprotocol#67, by @markafoltz.
-
Updates Method 2 for SSDP. w3c/openscreenprotocol#59, by @markafoltz.
-
Add text for SSDP licensing and security w3c/openscreenprotocol#58, by @markafoltz.
-
Add material around guest mode. w3c/openscreenprotocol#56, by @markafoltz.
-
-
7 pull requests merged.
-
Adds transport benchmark design w3c/openscreenprotocol#75.
-
Add Chrome OS to platform support w3c/openscreenprotocol#76.
-
Benchmark design for discovery protocols. w3c/openscreenprotocol#71.
-
Updates Method 2 for SSDP. w3c/openscreenprotocol#59.
-
Updates links to issues relating to performance data for discovery. w3c/openscreenprotocol#70.
-
Updates QUIC proposal. w3c/openscreenprotocol#67.
-
Add text for SSDP licensing and security w3c/openscreenprotocol#58.
-
-
1 pull request closed.
-
Add material around guest mode. w3c/openscreenprotocol#56.
-
-
7 pull requests received 26 new comments.
-
Benchmark design for discovery protocols. w3c/openscreenprotocol#71 (10 comments by @louaybassbouss, @markafoltz)
-
Add material around guest mode. w3c/openscreenprotocol#56 (9 comments by @anssiko, @chrisn, @louaybassbouss, @markafoltz, @schien)
-
Add text for SSDP licensing and security w3c/openscreenprotocol#58 (2 comments by @louaybassbouss, @markafoltz)
-
GitHub
w3c/remote-playback
-
3 issues opened.
-
Restrict the API to Secure Contexts or discuss the decision in Security Considerations w3c/remote-playback#107, by @jyasskin.
-
Add explicit text to define the disableRemotePlayback content attribute w3c/remote-playback#105, by @tidoust.
-
Use [Exposed=Window] w3c/remote-playback#103, by @anssiko.
-
-
2 issues closed.
-
Add explicit text to define the disableRemotePlayback content attribute w3c/remote-playback#105.
-
Use [Exposed=Window] w3c/remote-playback#103.
-
-
2 issues received 5 new comments.
-
Restrict the API to Secure Contexts or discuss the decision in Security Considerations w3c/remote-playback#107 (1 comment by @mounirlamouri)
-
2 pull requests opened.
-
Add disableRemotePlayback definition. w3c/remote-playback#106, by @markafoltz.
-
Use [Exposed=Window] w3c/remote-playback#104, by @anssiko.
-
-
2 pull requests merged.
-
Add disableRemotePlayback definition. w3c/remote-playback#106.
-
Use [Exposed=Window] w3c/remote-playback#104.
-
-
2 pull requests received 10 new comments.
-
Add disableRemotePlayback definition. w3c/remote-playback#106 (9 comments by @anssiko, @markafoltz, @tidoust)
-
w3c/openscreenprotocol
-
5 issues opened.
-
[Control Protocol] Cross reference control protocol messages with Presentation API steps w3c/openscreenprotocol#55, by @markafoltz.
-
Representation of BCP-47 language tags w3c/openscreenprotocol#54, by @markafoltz.
-
Remote CEC style control protocol w3c/openscreenprotocol#52, by @markafoltz.
-
Incorporate wake-on-lan into discovery protocol w3c/openscreenprotocol#51, by @markafoltz.
-
Editorial TODO: Add glossary reference and make language consistent w3c/openscreenprotocol#46, by @markafoltz.
-
-
2 issues closed.
-
Presentation API control protocol w3c/openscreenprotocol#11.
-
Editorial TODO: Add glossary reference and make language consistent w3c/openscreenprotocol#46.
-
-
1 issue received 1 new comment.
-
5 pull requests opened.
-
Adds Presentation Receiver status. w3c/openscreenprotocol#53, by @markafoltz.
-
Updates README.md. w3c/openscreenprotocol#50, by @markafoltz.
-
[Control Protocol] Adds messages for presentation connections. w3c/openscreenprotocol#49, by @markafoltz.
-
Define and use consistent terminology. w3c/openscreenprotocol#48, by @markafoltz.
-
Presentation connection request and response message definitions. w3c/openscreenprotocol#47, by @markafoltz.
-
-
6 pull requests merged.
-
Adds Presentation Receiver status. w3c/openscreenprotocol#53.
-
[Control Protocol] Adds messages for presentation connections. w3c/openscreenprotocol#49.
-
Updates README.md. w3c/openscreenprotocol#50.
-
Define and use consistent terminology. w3c/openscreenprotocol#48.
-
Presentation connection request and response message definitions. w3c/openscreenprotocol#47.
-
Issue 11 control protocol w3c/openscreenprotocol#44.
-
-
4 pull requests received 13 new comments.
-
Adds Presentation Receiver status. w3c/openscreenprotocol#53 (4 comments by @markafoltz, @tomoyukilabs)
-
Presentation connection request and response message definitions. w3c/openscreenprotocol#47 (1 comment by @markafoltz)
w3c/presentation-api
-
3 issues opened.
-
Presentation Testing API w3c/presentation-api#440, by @markafoltz.
-
Presentation of objects w3c/presentation-api#439, by @markafoltz.
-
Use [Exposed=Window] w3c/presentation-api#437, by @anssiko.
-
-
2 issues closed.
-
Use [Exposed=Window] w3c/presentation-api#437.
-
In receiver page, sandboxing flags do not fully block top-level navigation. w3c/presentation-api#434.
-
-
6 issues received 6 new comments.
-
Add facility for the opening page to add cloud paired screens as presentation targets w3c/presentation-api#61 (1 comment by @markafoltz)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (1 comment by @markafoltz)
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (1 comment by @markafoltz)
-
In receiver page, sandboxing flags do not fully block top-level navigation. w3c/presentation-api#434 (1 comment by @markafoltz)
-
2 pull requests opened.
-
Use [Exposed=Window] w3c/presentation-api#438, by @anssiko.
-
Clarifies restrictions on navigation in receiving browsing contexts. w3c/presentation-api#436, by @markafoltz.
-
-
2 pull requests merged.
-
Use [Exposed=Window] w3c/presentation-api#438.
-
Clarifies restrictions on navigation in receiving browsing contexts. w3c/presentation-api#436.
-
-
1 pull request received 3 new comments.
Participants
-
1 organization left.
-
Avaya Communications left.
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
[Protocol] Investigate variable length encodings for integer header values w3c/openscreenprotocol#45, by @markafoltz.
-
-
1 issue closed.
-
[mDNS] Investigate history of mDNS exploits / security flaws w3c/openscreenprotocol#39.
-
-
1 issue received 1 new comment.
-
[mDNS] Investigate history of mDNS exploits / security flaws w3c/openscreenprotocol#39 (1 comment by @markafoltz)
-
-
1 pull request opened.
-
Issue 11 control protocol w3c/openscreenprotocol#44, by @markafoltz.
-
-
1 pull request received 12 new comments.
-
Issue 11 control protocol w3c/openscreenprotocol#44 (12 comments by @anssiko, @chrisn, @markafoltz, @tidoust, @tomoyukilabs)
-
w3c/presentation-api
-
2 issues opened.
-
Add more explanation to examples w3c/presentation-api#435, by @chrisn.
-
In receiver page, sandboxing flags do not fully block top-level navigation. w3c/presentation-api#434, by @markafoltz.
-
-
2 issues received 3 new comments.
-
In receiver page, sandboxing flags do not fully block top-level navigation. w3c/presentation-api#434 (1 comment by @anssiko)
w3c/remote-playback
-
1 issue opened.
-
Adjust notes with normative content w3c/remote-playback#101, by @tidoust.
-
-
3 issues closed.
-
Adjust notes with normative content w3c/remote-playback#101.
-
Internationalization considerations w3c/remote-playback#66.
-
Should the ability to query by language or country be added to watchAvailability() w3c/remote-playback#70.
-
-
5 issues received 12 new comments.
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (3 comments by @anssiko, @markafoltz, @tidoust)
-
Should the ability to query by language or country be added to watchAvailability() w3c/remote-playback#70 (1 comment by @anssiko)
-
6 pull requests opened.
-
Adjust notes to clarify informative/normative intent w3c/remote-playback#102, by @tidoust.
-
Add i18n-related informative notes about locale passing between devices w3c/remote-playback#100, by @tidoust.
-
Fix #70: Note srclang hint to address i18n comment w3c/remote-playback#99, by @anssiko.
-
Remove RFC terms from the note, continued w3c/remote-playback#98, by @anssiko.
-
Remove RFC terms from the note w3c/remote-playback#97, by @anssiko.
-
Mark Anton Vayvod as former editor. w3c/remote-playback#96, by @mounirlamouri.
-
-
7 pull requests merged.
-
Add i18n-related informative notes about locale passing between devices w3c/remote-playback#100.
-
Adjust notes to clarify informative/normative intent w3c/remote-playback#102.
-
Fix #70: Note srclang hint to address i18n comment w3c/remote-playback#99.
-
Update SOTD to clarify the status of #41 w3c/remote-playback#95.
-
Remove RFC terms from the note, continued w3c/remote-playback#98.
-
Remove RFC terms from the note w3c/remote-playback#97.
-
Mark Anton Vayvod as former editor. w3c/remote-playback#96.
-
-
7 pull requests received 35 new comments.
-
Add i18n-related informative notes about locale passing between devices w3c/remote-playback#100 (13 comments by @anssiko, @markafoltz, @tidoust)
-
Adjust notes to clarify informative/normative intent w3c/remote-playback#102 (11 comments by @anssiko, @markafoltz, @tidoust)
-
Update SOTD to clarify the status of #41 w3c/remote-playback#95 (5 comments by @anssiko, @avayvod, @markafoltz, @mounirlamouri)
-
Fix #70: Note srclang hint to address i18n comment w3c/remote-playback#99 (3 comments by @anssiko, @markafoltz)
-
GitHub
w3c/openscreenprotocol
-
2 pull requests opened.
-
Adds mDNS security history and analysis. w3c/openscreenprotocol#43, by @markafoltz.
-
Minor wording corrections w3c/openscreenprotocol#42, by @chrisn.
-
-
2 pull requests merged.
-
Adds mDNS security history and analysis. w3c/openscreenprotocol#43.
-
Minor wording corrections w3c/openscreenprotocol#42.
-
-
1 pull request received 2 new comments.
-
Adds mDNS security history and analysis. w3c/openscreenprotocol#43 (2 comments by @chrisn, @markafoltz)
-
w3c/remote-playback
-
2 issues received 7 new comments.
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (5 comments by @markafoltz, @tidoust)
-
[meta] Publish Candidate Recommendation w3c/remote-playback#73 (2 comments by @mounirlamouri, @tidoust)
-
-
2 pull requests opened.
-
Update SOTD to clarify the status of #41 w3c/remote-playback#95, by @markafoltz.
-
Adds note regarding remote playback device capabilities. w3c/remote-playback#94, by @markafoltz.
-
-
1 pull request merged.
-
Adds note regarding remote playback device capabilities. w3c/remote-playback#94.
-
-
2 pull requests received 4 new comments.
-
Adds note regarding remote playback device capabilities. w3c/remote-playback#94 (3 comments by @avayvod, @markafoltz)
-
w3c/presentation-api
-
1 issue received 5 new comments.
-
[meta] Presentation API Testing w3c/presentation-api#266 (5 comments by @louaybassbouss, @markafoltz, @tomoyukilabs)
-
TR publications
-
1 document published.
-
Presentation API published as a Candidate Recommendation Snapshot. History of Presentation API
-
GitHub
w3c/remote-playback
-
3 issues opened.
-
Remote Playback API tests and implementation report w3c/remote-playback#92, by @Honry.
-
Remote playback device capabilities not always a subset of local playback device's w3c/remote-playback#88, by @anssiko.
-
Produce a preliminary implementation report w3c/remote-playback#87, by @anssiko.
-
-
7 issues closed.
-
Produce a preliminary implementation report w3c/remote-playback#87.
-
Clarify cross-element uniqueness requirements of callbackId w3c/remote-playback#85.
-
Notify callbacks when monitoring list of remote playback devices is stopped w3c/remote-playback#84.
-
[Privacy] Clarify that availability callback does not include human readable names w3c/remote-playback#82.
-
[Privacy] Clarify steps to generate callbackId w3c/remote-playback#81.
-
Implementation guidance for browsers when a media element with controls is remoted w3c/remote-playback#48.
-
[Privacy] Request to disable monitoring when disableRemotePlayback is set w3c/remote-playback#80.
-
-
10 issues received 24 new comments.
-
Produce a preliminary implementation report w3c/remote-playback#87 (9 comments by @anssiko, @avayvod, @Honry, @mounirlamouri)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (4 comments by @anssiko, @mounirlamouri)
-
Clarify cross-element uniqueness requirements of callbackId w3c/remote-playback#85 (1 comment by @markafoltz)
-
Notify callbacks when monitoring list of remote playback devices is stopped w3c/remote-playback#84 (1 comment by @markafoltz)
-
[Privacy] Clarify that availability callback does not include human readable names w3c/remote-playback#82 (1 comment by @markafoltz)
-
Implementation guidance for browsers when a media element with controls is remoted w3c/remote-playback#48 (1 comment by @markafoltz)
-
[Privacy] Request to disable monitoring when disableRemotePlayback is set w3c/remote-playback#80 (1 comment by @markafoltz)
-
-
5 pull requests opened.
-
Fix #87: Add preliminary implementation report w3c/remote-playback#93, by @anssiko.
-
Clarifies handling of availability callbacks when monitoring is stopped. w3c/remote-playback#91, by @markafoltz.
-
Clarifies callbackId requirements. w3c/remote-playback#90, by @markafoltz.
-
Add "Candidate Recommendation exit criteria" section w3c/remote-playback#89, by @tidoust.
-
Align repo administrivia with W3C baseline w3c/remote-playback#86, by @dontcallmedom.
-
-
6 pull requests merged.
-
Fix #87: Add preliminary implementation report w3c/remote-playback#93.
-
Clarifies handling of availability callbacks when monitoring is stopped. w3c/remote-playback#91.
-
Clarifies callbackId requirements. w3c/remote-playback#90.
-
Add "Candidate Recommendation exit criteria" section w3c/remote-playback#89.
-
[Privacy] Adds notes clarifying behavior to address privacy review. w3c/remote-playback#83.
-
Align repo administrivia with W3C baseline w3c/remote-playback#86.
-
-
3 pull requests received 8 new comments.
-
Fix #87: Add preliminary implementation report w3c/remote-playback#93 (5 comments by @anssiko, @Honry)
-
[Privacy] Adds notes clarifying behavior to address privacy review. w3c/remote-playback#83 (2 comments by @anssiko, @markafoltz)
-
w3c/presentation-api
-
1 issue closed.
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406.
-
-
2 issues received 4 new comments.
-
[meta] Presentation API Testing w3c/presentation-api#266 (3 comments by @louaybassbouss, @markafoltz, @tidoust)
-
-
1 pull request opened.
-
Align repo administrivia with W3C baseline w3c/presentation-api#433, by @dontcallmedom.
-
-
1 pull request merged.
-
Align repo administrivia with W3C baseline w3c/presentation-api#433.
-
w3c/openscreenprotocol
-
4 issues opened.
-
[v2] Propose guest mode mechanism w3c/openscreenprotocol#41, by @markafoltz.
-
[mDNS] Investigate history of mDNS exploits / security flaws w3c/openscreenprotocol#39, by @markafoltz.
-
[mDNS] Get network efficiency data w3c/openscreenprotocol#38, by @markafoltz.
-
[mDNS] Get reliability data w3c/openscreenprotocol#37, by @markafoltz.
-
-
3 issues closed.
-
[Meta] Evaluate protocol transport mechanisms w3c/openscreenprotocol#8.
-
Evaluate Mozilla proposal as a protocol transport w3c/openscreenprotocol#10.
-
Evaluate Multicast DNS/DNS-SD as a discovery mechanism w3c/openscreenprotocol#6.
-
-
5 issues received 6 new comments.
-
[Meta] Write document describing protocol requirements w3c/openscreenprotocol#1 (2 comments by @louaybassbouss, @markafoltz)
-
Evaluate Mozilla proposal as a protocol transport w3c/openscreenprotocol#10 (1 comment by @markafoltz)
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (1 comment by @markafoltz)
-
Evaluate Multicast DNS/DNS-SD as a discovery mechanism w3c/openscreenprotocol#6 (1 comment by @markafoltz)
-
-
1 pull request opened.
-
[mdns] Evaluation of mDNS/DNS-SD as an implementation of Open Screen discovery w3c/openscreenprotocol#40, by @markafoltz.
-
-
1 pull request merged.
-
[mdns] Evaluation of mDNS/DNS-SD as an implementation of Open Screen discovery w3c/openscreenprotocol#40.
-
-
1 pull request received 2 new comments.
-
[mdns] Evaluation of mDNS/DNS-SD as an implementation of Open Screen discovery w3c/openscreenprotocol#40 (2 comments by @markafoltz, @schien)
-
GitHub
w3c/openscreenprotocol
-
7 issues opened.
-
[DataChannel] Obtain data on network and power efficiency w3c/openscreenprotocol#33, by @markafoltz.
-
[DataChannel] Obtain data on hardware requirements w3c/openscreenprotocol#32, by @markafoltz.
-
[DataChannel] Get data on connection and message latency w3c/openscreenprotocol#31, by @markafoltz.
-
[DataChannel] Get reliability data. w3c/openscreenprotocol#30, by @markafoltz.
-
[SSDP] Investigate licensing requirements for uPnP w3c/openscreenprotocol#27, by @markafoltz.
-
[SSDP] Get network and power efficiency data w3c/openscreenprotocol#26, by @markafoltz.
-
[SSDP] Research history of uPnP exploits w3c/openscreenprotocol#25, by @markafoltz.
-
-
1 issue closed.
-
[SSDP] Evaluate power requirements for SSDP discovery w3c/openscreenprotocol#23.
-
-
2 issues received 2 new comments.
-
[SSDP] Evaluate power requirements for SSDP discovery w3c/openscreenprotocol#23 (1 comment by @markafoltz)
-
5 pull requests opened.
-
Reformat ssdp.md according to templates/discovery.md w3c/openscreenprotocol#36, by @markafoltz.
-
Adds template for discovery & tweak transport template w3c/openscreenprotocol#35, by @markafoltz.
-
Make edits w3c/openscreenprotocol#34, by @markafoltz.
-
SSDP: A couple of more edits. w3c/openscreenprotocol#29, by @markafoltz.
-
[SSDP] Editing to SSDP evaluation. w3c/openscreenprotocol#28, by @markafoltz.
-
-
5 pull requests merged.
-
Reformat ssdp.md according to templates/discovery.md w3c/openscreenprotocol#36.
-
Adds template for discovery & tweak transport template w3c/openscreenprotocol#35.
-
Make edits w3c/openscreenprotocol#34.
-
SSDP: A couple of more edits. w3c/openscreenprotocol#29.
-
[SSDP] Editing to SSDP evaluation. w3c/openscreenprotocol#28.
-
-
1 pull request reopened.
-
Adds template for discovery & tweak transport template w3c/openscreenprotocol#35, by @markafoltz.
-
-
4 pull requests received 5 new comments.
-
Reformat ssdp.md according to templates/discovery.md w3c/openscreenprotocol#36 (1 comment by @louaybassbouss)
-
Adds template for discovery & tweak transport template w3c/openscreenprotocol#35 (1 comment by @markafoltz)
w3c/remote-playback
-
5 issues opened.
-
Clarify cross-element uniqueness requirements of callbackId w3c/remote-playback#85, by @markafoltz.
-
Notify callbacks when monitoring list of remote playback devices is stopped w3c/remote-playback#84, by @markafoltz.
-
[Privacy] Clarify that availability callback does not include human readable names w3c/remote-playback#82, by @markafoltz.
-
[Privacy] Clarify steps to generate callbackId w3c/remote-playback#81, by @markafoltz.
-
[Privacy] Request to disable monitoring when disableRemotePlayback is set w3c/remote-playback#80, by @markafoltz.
-
-
2 issues closed.
-
Define what should happen when device gets disconnected while playing w3c/remote-playback#56.
-
Merge steps 5 and 9 for prompt() algorithm w3c/remote-playback#64.
-
-
8 issues received 39 new comments.
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46 (7 comments by @avayvod, @chrisn, @markafoltz)
-
[meta] Publish Candidate Recommendation w3c/remote-playback#73 (7 comments by @anssiko, @avayvod, @markafoltz)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (6 comments by @anssiko, @avayvod, @markafoltz)
-
Notify callbacks when monitoring list of remote playback devices is stopped w3c/remote-playback#84 (5 comments by @avayvod, @markafoltz)
-
[Privacy] Clarify steps to generate callbackId w3c/remote-playback#81 (5 comments by @avayvod, @markafoltz)
-
Should the ability to query by language or country be added to watchAvailability() w3c/remote-playback#70 (4 comments by @avayvod, @markafoltz, @steveatkin)
-
[Privacy] Request to disable monitoring when disableRemotePlayback is set w3c/remote-playback#80 (3 comments by @avayvod, @markafoltz)
-
Merge steps 5 and 9 for prompt() algorithm w3c/remote-playback#64 (2 comments by @avayvod, @markafoltz)
-
-
6 pull requests opened.
-
[Privacy] Adds notes clarifying behavior to address privacy review. w3c/remote-playback#83, by @markafoltz.
-
Adds notes about controls and playback. w3c/remote-playback#79, by @markafoltz.
-
Drop step 9 in prompt() w3c/remote-playback#78, by @markafoltz.
-
Add note ordering availaiblity callbacks and disconnect event. w3c/remote-playback#77, by @markafoltz.
-
Swaps steps 5 and 6 in the prompt() algorithm. w3c/remote-playback#76, by @markafoltz.
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/remote-playback#75, by @tidoust.
-
-
5 pull requests merged.
-
Adds notes about controls and playback. w3c/remote-playback#79.
-
Add note ordering availaiblity callbacks and disconnect event. w3c/remote-playback#77.
-
Drop step 9 in prompt() w3c/remote-playback#78.
-
Swaps steps 5 and 6 in the prompt() algorithm. w3c/remote-playback#76.
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/remote-playback#75.
-
-
5 pull requests received 18 new comments.
-
[Privacy] Adds notes clarifying behavior to address privacy review. w3c/remote-playback#83 (12 comments by @avayvod, @markafoltz)
-
Adds notes about controls and playback. w3c/remote-playback#79 (3 comments by @avayvod, @markafoltz)
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/remote-playback#75 (1 comment by @markafoltz)
-
w3c/presentation-api
-
2 issues closed.
-
Introduction could use some copy editing w3c/presentation-api#345.
-
Relax `terminate` algorithm to deal with other states? w3c/presentation-api#421.
-
-
3 issues received 20 new comments.
-
[meta] Presentation API Testing w3c/presentation-api#266 (8 comments by @markafoltz, @tidoust, @tomoyukilabs)
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406 (7 comments by @anssiko, @louaybassbouss, @markafoltz, @tidoust)
-
Relax `terminate` algorithm to deal with other states? w3c/presentation-api#421 (5 comments by @anssiko, @markafoltz, @tidoust)
-
-
6 pull requests opened.
-
Minor changes to Introduction section w3c/presentation-api#432, by @chrisn.
-
Fix broken fragments reported by Link Checker w3c/presentation-api#431, by @anssiko.
-
Fix group name and update changelog w3c/presentation-api#430, by @tidoust.
-
Copy editing of non-normative text w3c/presentation-api#429, by @markafoltz.
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/presentation-api#428, by @tidoust.
-
Allow termination via connections in a connecting state. w3c/presentation-api#427, by @markafoltz.
-
-
6 pull requests merged.
-
Minor changes to Introduction section w3c/presentation-api#432.
-
Fix broken fragments reported by Link Checker w3c/presentation-api#431.
-
Fix group name and update changelog w3c/presentation-api#430.
-
Copy editing of non-normative text w3c/presentation-api#429.
-
Allow termination via connections in a connecting state. w3c/presentation-api#427.
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/presentation-api#428.
-
-
5 pull requests received 11 new comments.
-
Copy editing of non-normative text w3c/presentation-api#429 (7 comments by @anssiko, @markafoltz, @tidoust)
-
Tell ReSpec to use W3C Software and Document License for the spec w3c/presentation-api#428 (1 comment by @markafoltz)
-
Allow termination via connections in a connecting state. w3c/presentation-api#427 (1 comment by @tidoust)
-
GitHub
w3c/remote-playback
-
1 issue opened.
-
Interoperability concerns by lack of a common denominator in transport w3c/remote-playback#74, by @cynthia.
-
-
2 issues received 6 new comments.
-
Interoperability concerns by lack of a common denominator in transport w3c/remote-playback#74 (5 comments by @avayvod, @cynthia, @dbaron, @mounirlamouri)
-
w3c/presentation-api
-
4 issues opened.
-
Termination should also "discard" the receiving browsing context w3c/presentation-api#423, by @tidoust.
-
Turn SHOULD into MUST for close/terminate messages handling? w3c/presentation-api#422, by @tidoust.
-
Relax `terminate` algorithm to deal with other states? w3c/presentation-api#421, by @tidoust.
-
Behavior of a receiving user agent in reconnecting w3c/presentation-api#419, by @tomoyukilabs.
-
-
3 issues closed.
-
Behavior of a receiving user agent in reconnecting w3c/presentation-api#419.
-
Turn SHOULD into MUST for close/terminate messages handling? w3c/presentation-api#422.
-
Termination should also "discard" the receiving browsing context w3c/presentation-api#423.
-
-
5 issues received 15 new comments.
-
Behavior of a receiving user agent in reconnecting w3c/presentation-api#419 (5 comments by @markafoltz, @schien, @tomoyukilabs)
-
Turn SHOULD into MUST for close/terminate messages handling? w3c/presentation-api#422 (4 comments by @markafoltz, @tomoyukilabs)
-
Relax `terminate` algorithm to deal with other states? w3c/presentation-api#421 (2 comments by @markafoltz)
-
Termination should also "discard" the receiving browsing context w3c/presentation-api#423 (1 comment by @markafoltz)
-
-
4 pull requests opened.
-
Remove closed connections from the set of presentation controllers. w3c/presentation-api#426, by @markafoltz.
-
Change SHOULD to MUST when closing or terminating connections. w3c/presentation-api#425, by @markafoltz.
-
Add steps to discard the receiving browsing context. w3c/presentation-api#424, by @markafoltz.
-
Dropped sandboxing section, referencing HTML 5.2 instead w3c/presentation-api#420, by @tidoust.
-
-
5 pull requests merged.
-
Remove closed connections from the set of presentation controllers. w3c/presentation-api#426.
-
Change SHOULD to MUST when closing or terminating connections. w3c/presentation-api#425.
-
Add steps to discard the receiving browsing context. w3c/presentation-api#424.
-
Dropped sandboxing section, referencing HTML 5.2 instead w3c/presentation-api#420.
-
Relaxed CR exit criteria to match known implementation plans w3c/presentation-api#418.
-
-
4 pull requests received 7 new comments.
-
Relaxed CR exit criteria to match known implementation plans w3c/presentation-api#418 (4 comments by @anssiko, @schien, @tidoust)
-
Change SHOULD to MUST when closing or terminating connections. w3c/presentation-api#425 (1 comment by @tidoust)
-
Remove closed connections from the set of presentation controllers. w3c/presentation-api#426 (1 comment by @tomoyukilabs)
-
Dropped sandboxing section, referencing HTML 5.2 instead w3c/presentation-api#420 (1 comment by @markafoltz)
-
w3c/openscreenprotocol
-
1 pull request merged.
-
initial draft for evaluating Data Channel as the transport protocol. w3c/openscreenprotocol#24.
-
-
1 pull request received 15 new comments.
-
initial draft for evaluating Data Channel as the transport protocol. w3c/openscreenprotocol#24 (15 comments by @anssiko, @markafoltz, @schien)
-
GitHub
w3c/presentation-api
-
2 issues closed.
-
[ReSpec] Performance regression when loading spec over file:/// w3c/presentation-api#412.
-
Receiving browsing context needs additional flags set w3c/presentation-api#414.
-
-
3 issues received 23 new comments.
-
Receiving browsing context needs additional flags set w3c/presentation-api#414 (12 comments by @anssiko, @markafoltz, @schien, @tidoust, @tomoyukilabs)
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406 (8 comments by @anssiko, @markafoltz, @tidoust)
-
[ReSpec] Performance regression when loading spec over file:/// w3c/presentation-api#412 (3 comments by @anssiko, @markafoltz)
-
-
4 pull requests opened.
-
Relaxed CR exit criteria to match known implementation plans w3c/presentation-api#418, by @tidoust.
-
Adds notes related to sandboxing flags on presentations w3c/presentation-api#417, by @markafoltz.
-
Updated list of changes since previous CR w3c/presentation-api#416, by @tidoust.
-
Sets top-level navigation and modal dialog flags on presentations. w3c/presentation-api#415, by @markafoltz.
-
-
3 pull requests merged.
-
Adds notes related to sandboxing flags on presentations w3c/presentation-api#417.
-
Updated list of changes since previous CR w3c/presentation-api#416.
-
Sets top-level navigation and modal dialog flags on presentations. w3c/presentation-api#415.
-
-
4 pull requests received 7 new comments.
-
Sets top-level navigation and modal dialog flags on presentations. w3c/presentation-api#415 (3 comments by @anssiko, @markafoltz, @tidoust)
-
Relaxed CR exit criteria to match known implementation plans w3c/presentation-api#418 (2 comments by @anssiko, @markafoltz)
-
Adds notes related to sandboxing flags on presentations w3c/presentation-api#417 (1 comment by @tidoust)
-
w3c/openscreenprotocol
-
3 issues opened.
-
[SSDP] Evaluate power requirements for SSDP discovery w3c/openscreenprotocol#23, by @markafoltz.
-
[SSDP] Ensure that advertised friendly names are i18n capable w3c/openscreenprotocol#22, by @markafoltz.
-
[SSDP] Investigate mechanisms to pre-filter devices by Presentation URL w3c/openscreenprotocol#21, by @markafoltz.
-
-
1 issue closed.
-
Evaluate SSDP/DIAL as a discovery mechanism w3c/openscreenprotocol#7.
-
-
4 issues received 7 new comments.
-
[SSDP] Ensure that advertised friendly names are i18n capable w3c/openscreenprotocol#22 (3 comments by @louaybassbouss, @markafoltz, @tomoyukilabs)
-
Evaluate SSDP/DIAL as a discovery mechanism w3c/openscreenprotocol#7 (2 comments by @louaybassbouss, @markafoltz)
-
[SSDP] Evaluate power requirements for SSDP discovery w3c/openscreenprotocol#23 (1 comment by @louaybassbouss)
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (1 comment by @louaybassbouss)
-
-
2 pull requests opened.
-
initial draft for evaluating Data Channel as the transport protocol. w3c/openscreenprotocol#24, by @schien.
-
create a new document ssdp.md that evaluates SSDP protocol w3c/openscreenprotocol#20, by @louaybassbouss.
-
-
1 pull request merged.
-
create a new document ssdp.md that evaluates SSDP protocol w3c/openscreenprotocol#20.
-
-
1 pull request received 30 new comments.
-
create a new document ssdp.md that evaluates SSDP protocol w3c/openscreenprotocol#20 (30 comments by @louaybassbouss, @markafoltz)
-
w3c/remote-playback
-
1 issue opened.
-
[meta] Publish Candidate Recommendation w3c/remote-playback#73, by @anssiko.
-
-
1 issue received 6 new comments.
-
Define the interaction with Media Session w3c/remote-playback#10 (6 comments by @avayvod, @chrisn, @markafoltz, @mounirlamouri)
-
GitHub
w3c/presentation-api
-
2 issues opened.
-
Receiving browsing context needs additional flags set w3c/presentation-api#414, by @markafoltz.
-
[ReSpec] Performance regression when loading spec over file:/// w3c/presentation-api#412, by @markafoltz.
-
-
3 issues closed.
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380.
-
Reference to WebIDL w3c/presentation-api#408.
-
PresentationReceiver.connectionList can't be [SameObject] anymore w3c/presentation-api#407.
-
-
6 issues received 26 new comments.
-
[meta] Presentation API Testing w3c/presentation-api#266 (9 comments by @anssiko, @markafoltz, @tomoyukilabs)
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380 (6 comments by @anssiko, @markafoltz)
-
[ReSpec] Performance regression when loading spec over file:/// w3c/presentation-api#412 (4 comments by @anssiko, @marcoscaceres)
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406 (3 comments by @anssiko, @markafoltz)
-
Receiving browsing context needs additional flags set w3c/presentation-api#414 (2 comments by @anssiko, @markafoltz)
-
-
4 pull requests opened.
-
Restrict API to secure contexts w3c/presentation-api#413, by @markafoltz.
-
Fix WebIDL references w3c/presentation-api#411, by @anssiko.
-
Update Service Worker references w3c/presentation-api#410, by @tomoyukilabs.
-
Remove [SameObject] from receiver.connectionList w3c/presentation-api#409, by @markafoltz.
-
-
4 pull requests merged.
-
Restrict API to secure contexts w3c/presentation-api#413.
-
Fix WebIDL references w3c/presentation-api#411.
-
Update Service Worker references w3c/presentation-api#410.
-
Remove [SameObject] from receiver.connectionList w3c/presentation-api#409.
-
-
3 pull requests received 9 new comments.
-
Restrict API to secure contexts w3c/presentation-api#413 (5 comments by @annevk, @anssiko, @markafoltz, @tidoust)
-
w3c/remote-playback
-
1 pull request opened.
-
Add missing definitions, fix ReSpec & validator warnings w3c/remote-playback#72, by @anssiko.
-
-
1 pull request merged.
-
Add missing definitions, fix ReSpec & validator warnings w3c/remote-playback#72.
-
-
1 pull request received 7 new comments.
-
Add missing definitions, fix ReSpec & validator warnings w3c/remote-playback#72 (7 comments by @anssiko, @avayvod, @mounirlamouri)
-
GitHub
w3c/presentation-api
-
3 issues opened.
-
Reference to WebIDL w3c/presentation-api#408, by @tidoust.
-
PresentationReceiver.connectionList can't be [SameObject] anymore w3c/presentation-api#407, by @bzbarsky.
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406, by @anssiko.
-
-
3 issues closed.
-
Check references category and stability w3c/presentation-api#295.
-
Migrate HTML 5.0 references to HTML 5.1? w3c/presentation-api#396.
-
Make sure all IDL members have "dfn" in prose w3c/presentation-api#397.
-
-
1 issue reopened.
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380, by @markafoltz.
-
-
6 issues received 24 new comments.
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380 (9 comments by @anssiko, @markafoltz)
-
PresentationReceiver.connectionList can't be [SameObject] anymore w3c/presentation-api#407 (6 comments by @anssiko, @bzbarsky, @markafoltz)
-
[meta] Publish a revised Candidate Recommendation w3c/presentation-api#406 (4 comments by @anssiko, @tidoust)
-
Check references category and stability w3c/presentation-api#295 (3 comments by @markafoltz, @tidoust)
-
-
3 pull requests opened.
-
Added change log section with list of changes since first CR w3c/presentation-api#405, by @tidoust.
-
Issue #396: Migrate HTML 5.0 references to HTML 5.1 w3c/presentation-api#404, by @tidoust.
-
Issue #397 - Make sur all IDL terms have <dfn> in prose w3c/presentation-api#403, by @tidoust.
-
-
3 pull requests merged.
-
Added change log section with list of changes since first CR w3c/presentation-api#405.
-
Issue #396: Migrate HTML 5.0 references to HTML 5.1 w3c/presentation-api#404.
-
Issue #397 - Make sur all IDL terms have <dfn> in prose w3c/presentation-api#403.
-
-
3 pull requests received 15 new comments.
-
Issue #396: Migrate HTML 5.0 references to HTML 5.1 w3c/presentation-api#404 (9 comments by @markafoltz, @tidoust)
-
Added change log section with list of changes since first CR w3c/presentation-api#405 (3 comments by @anssiko, @markafoltz, @tidoust)
-
Issue #397 - Make sur all IDL terms have <dfn> in prose w3c/presentation-api#403 (3 comments by @markafoltz, @tidoust)
-
w3c/remote-playback
-
2 issues opened.
-
<EDITED TITLE> w3c/remote-playback#71, by @sompor1992.
-
Should the ability to query by language or country be added to watchAvailability() w3c/remote-playback#70, by @stevenatkin.
-
-
1 issue closed.
-
<EDITED TITLE> w3c/remote-playback#71.
-
w3c/openscreenprotocol
-
3 issues closed.
-
Non-functional requirements w3c/openscreenprotocol#4.
-
Requirements: Presentation API w3c/openscreenprotocol#2.
-
Evaluate QUIC as a protocol transport w3c/openscreenprotocol#9.
-
-
7 issues received 10 new comments.
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (2 comments by @chrisn, @louaybassbouss)
-
[Control Protocol] Remote Playback API control protocol w3c/openscreenprotocol#12 (1 comment by @anssiko)
-
[Meta] Write document describing protocol requirements w3c/openscreenprotocol#1 (1 comment by @louaybassbouss)
-
5 pull requests opened.
-
Addresses Issue #4: Adds a note about extensibility. w3c/openscreenprotocol#19, by @markafoltz.
-
Issue 9 quic w3c/openscreenprotocol#18, by @markafoltz.
-
Draft evaluation for QUIC. w3c/openscreenprotocol#17, by @markafoltz.
-
Template for transport evaluation w3c/openscreenprotocol#16, by @markafoltz.
-
Adds non-functional requirements for user experience. Additional editing. w3c/openscreenprotocol#15, by @markafoltz.
-
-
5 pull requests merged.
-
Addresses Issue #4: Adds a note about extensibility. w3c/openscreenprotocol#19.
-
Issue 9 quic w3c/openscreenprotocol#18.
-
Draft evaluation for QUIC. w3c/openscreenprotocol#17.
-
Template for transport evaluation w3c/openscreenprotocol#16.
-
Adds non-functional requirements for user experience. Additional editing. w3c/openscreenprotocol#15.
-
-
3 pull requests received 13 new comments.
-
Adds non-functional requirements for user experience. Additional editing. w3c/openscreenprotocol#15 (5 comments by @anssiko, @markafoltz, @schien)