Second Screen Working Group - Activity in 2016
No matches.
GitHub
w3c/presentation-api
-
10 issues opened.
-
Sandboxing steps in start, reconnect, getAvailability are now useless w3c/presentation-api#398, by @tidoust.
-
Make sure all IDL members have "dfn" in prose w3c/presentation-api#397, by @tidoust.
-
Migrate HTML 5.0 references to HTML 5.1? w3c/presentation-api#396, by @markafoltz.
-
Make select algo reject in ancestor and descendant browsing contexts w3c/presentation-api#394, by @tidoust.
-
Steps that re-use objects should specify the relevant settings object/Javascript Realm w3c/presentation-api#391, by @markafoltz.
-
Check on Presentation display availability in getAvailability can never be true w3c/presentation-api#388, by @tidoust.
-
Filling out the list of available presentation displays for start w3c/presentation-api#387, by @tidoust.
-
Drop step 6 of getAvailability for consistency with start? w3c/presentation-api#383, by @tidoust.
-
Wrong use of "available presentation displays" in 6.4.4 w3c/presentation-api#382, by @tidoust.
-
Step 11 of getAvailability should not run "in parallel" w3c/presentation-api#381, by @tidoust.
-
-
12 issues closed.
-
Make select algo reject in ancestor and descendant browsing contexts w3c/presentation-api#394.
-
Steps that re-use objects should specify the relevant settings object/Javascript Realm w3c/presentation-api#391.
-
Sandboxing steps in start, reconnect, getAvailability are now useless w3c/presentation-api#398.
-
Step 11 of getAvailability should not run "in parallel" w3c/presentation-api#381.
-
Filling out the list of available presentation displays for start w3c/presentation-api#387.
-
Check on Presentation display availability in getAvailability can never be true w3c/presentation-api#388.
-
Well defined environment for nested contexts of the receiving browsing context? w3c/presentation-api#367.
-
Clarify event order when establishing a presentation connection w3c/presentation-api#360.
-
Investigate if sandboxing flag check can move to the PresentationRequest ctor w3c/presentation-api#379.
-
Determine if we need to fire a terminated event in the receiving browsing context(s) w3c/presentation-api#374.
-
Wrong use of "available presentation displays" in 6.4.4 w3c/presentation-api#382.
-
Drop step 6 of getAvailability for consistency with start? w3c/presentation-api#383.
-
-
12 issues received 25 new comments.
-
Step 11 of getAvailability should not run "in parallel" w3c/presentation-api#381 (5 comments by @markafoltz, @tidoust)
-
Check on Presentation display availability in getAvailability can never be true w3c/presentation-api#388 (5 comments by @markafoltz, @tidoust)
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380 (3 comments by @annevk, @markafoltz)
-
Filling out the list of available presentation displays for start w3c/presentation-api#387 (3 comments by @markafoltz, @tidoust)
-
Sandboxing steps in start, reconnect, getAvailability are now useless w3c/presentation-api#398 (1 comment by @markafoltz)
-
Well defined environment for nested contexts of the receiving browsing context? w3c/presentation-api#367 (1 comment by @markafoltz)
-
Make select algo reject in ancestor and descendant browsing contexts w3c/presentation-api#394 (1 comment by @markafoltz)
-
Investigate if sandboxing flag check can move to the PresentationRequest ctor w3c/presentation-api#379 (1 comment by @markafoltz)
-
Wrong use of "available presentation displays" in 6.4.4 w3c/presentation-api#382 (1 comment by @markafoltz)
-
Drop step 6 of getAvailability for consistency with start? w3c/presentation-api#383 (1 comment by @markafoltz)
-
Clarify event order when establishing a presentation connection w3c/presentation-api#360 (1 comment by @tidoust)
-
-
12 pull requests opened.
-
Addresses Issue #394: Reject start() in all browsing contexts w3c/presentation-api#402, by @markafoltz.
-
Adds a note about display of origins that are not potentially trustworthy. w3c/presentation-api#401, by @markafoltz.
-
Addresses Issue #391 w3c/presentation-api#400, by @markafoltz.
-
Addresses Issue #398: Sandboxing steps in start, reconnect, getAvailability are now useless w3c/presentation-api#399, by @markafoltz.
-
Addresses Issue 367 w3c/presentation-api#395, by @markafoltz.
-
Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason w3c/presentation-api#393, by @foolip.
-
Issue #387: Monitoring algo takes pending request to start into account w3c/presentation-api#392, by @tidoust.
-
Issue 387: Need to make sure we have a display list for start(). w3c/presentation-api#390, by @markafoltz.
-
Issue #360: Adds a presentation task source w3c/presentation-api#389, by @markafoltz.
-
Sets the state of receiving presentation connections to terminated before unload. w3c/presentation-api#386, by @markafoltz.
-
Issue #379: Adds sandboxing flag check to PresentationRequest ctor. w3c/presentation-api#385, by @markafoltz.
-
Addresses Issues 382 and 383 on the steps to get presentation displays. w3c/presentation-api#384, by @markafoltz.
-
-
11 pull requests merged.
-
Adds a note about display of origins that are not potentially trustworthy. w3c/presentation-api#401.
-
Addresses Issue #394: Reject start() in all browsing contexts w3c/presentation-api#402.
-
Addresses Issue #391 w3c/presentation-api#400.
-
Addresses Issue #398: Sandboxing steps in start, reconnect, getAvailability are now useless w3c/presentation-api#399.
-
Issue #387: Monitoring algo takes pending request to start into account w3c/presentation-api#392.
-
Addresses Issue 367 w3c/presentation-api#395.
-
Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason w3c/presentation-api#393.
-
Issue #360: Adds a presentation task source w3c/presentation-api#389.
-
Issue #379: Adds sandboxing flag check to PresentationRequest ctor. w3c/presentation-api#385.
-
Sets the state of receiving presentation connections to terminated before unload. w3c/presentation-api#386.
-
Addresses Issues 382 and 383 on the steps to get presentation displays. w3c/presentation-api#384.
-
-
1 pull request closed.
-
Issue 387: Need to make sure we have a display list for start(). w3c/presentation-api#390.
-
-
8 pull requests received 44 new comments.
-
Issue #387: Monitoring algo takes pending request to start into account w3c/presentation-api#392 (29 comments by @markafoltz, @tidoust)
-
Issue 387: Need to make sure we have a display list for start(). w3c/presentation-api#390 (5 comments by @markafoltz, @tidoust)
-
Addresses Issues 382 and 383 on the steps to get presentation displays. w3c/presentation-api#384 (2 comments by @markafoltz, @tidoust)
-
Adds a note about display of origins that are not potentially trustworthy. w3c/presentation-api#401 (1 comment by @tidoust)
-
Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason w3c/presentation-api#393 (1 comment by @markafoltz)
-
Sets the state of receiving presentation connections to terminated before unload. w3c/presentation-api#386 (1 comment by @tidoust)
-
Issue #379: Adds sandboxing flag check to PresentationRequest ctor. w3c/presentation-api#385 (1 comment by @tidoust)
-
w3c/openscreenprotocol
-
2 issues received 6 new comments.
-
[Meta] Propose security mechanisms for Open Screen protocol w3c/openscreenprotocol#13 (5 comments by @chrisn, @markafoltz, @mwatson2, @tomoyukilabs)
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (1 comment by @mwatson2)
-
-
1 pull request opened.
-
Initial draft of Open Screen requirements. w3c/openscreenprotocol#14, by @markafoltz.
-
-
1 pull request merged.
-
Initial draft of Open Screen requirements. w3c/openscreenprotocol#14.
-
-
1 pull request received 10 new comments.
-
Initial draft of Open Screen requirements. w3c/openscreenprotocol#14 (10 comments by @markafoltz, @tidoust)
-
w3c/remote-playback
-
1 issue received 1 new comment.
Lifecycle
-
1 charter started.
-
Chartered until 31 October 2017.
-
TR publications
-
1 document published.
-
Remote Playback API published as a Working Draft. History of Remote Playback API
-
GitHub
w3c/presentation-api
-
7 issues opened.
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380, by @markafoltz.
-
Investigate if sandboxing flag check can move to the PresentationRequest ctor w3c/presentation-api#379, by @markafoltz.
-
Determine if we need to fire a terminated event in the receiving browsing context(s) w3c/presentation-api#374, by @markafoltz.
-
Well defined environment for nested contexts of the receiving browsing context? w3c/presentation-api#367, by @tidoust.
-
Steps to reconnect to a presentation assume there's already a PresentationConnection w3c/presentation-api#366, by @markafoltz.
-
[SameObject] for receiver seems wrong w3c/presentation-api#365, by @annevk.
-
-
9 issues closed.
-
Consider checking for security context in the PresentationRequest constructor w3c/presentation-api#362.
-
Clarify arguments to getting presentation displays availability information w3c/presentation-api#363.
-
"setting presentation.defaultRequest will have no effect" note is ambiguous w3c/presentation-api#359.
-
define the behavior for consecutive |getAvailability| w3c/presentation-api#335.
-
[SameObject] for receiver seems wrong w3c/presentation-api#365.
-
Use USVString for URLs w3c/presentation-api#361.
-
Steps to reconnect to a presentation assume there's already a PresentationConnection w3c/presentation-api#366.
-
setConnection in example 5.5 may put UI in an inconsistent state w3c/presentation-api#339.
-
-
13 issues received 45 new comments.
-
Consider checking for security context in the PresentationRequest constructor w3c/presentation-api#362 (10 comments by @annevk, @markafoltz, @mikewest, @tidoust)
-
[SameObject] for receiver seems wrong w3c/presentation-api#365 (9 comments by @annevk, @markafoltz, @tidoust)
-
Clarify event order when establishing a presentation connection w3c/presentation-api#360 (7 comments by @annevk, @markafoltz, @tidoust)
-
"setting presentation.defaultRequest will have no effect" note is ambiguous w3c/presentation-api#359 (4 comments by @louaybassbouss, @markafoltz)
-
Authenticity of screen selection permission is problematic in insecure contexts w3c/presentation-api#380 (3 comments by @annevk, @markafoltz)
-
Investigate if sandboxing flag check can move to the PresentationRequest ctor w3c/presentation-api#379 (2 comments by @annevk, @mounirlamouri)
-
Well defined environment for nested contexts of the receiving browsing context? w3c/presentation-api#367 (2 comments by @markafoltz)
-
Determine if we need to fire a terminated event in the receiving browsing context(s) w3c/presentation-api#374 (2 comments by @markafoltz)
-
It is unclear what "If there is already an unsettled Promise from a previous call to start for the same controlling browsing context" means" w3c/presentation-api#364 (2 comments by @markafoltz)
-
Steps to reconnect to a presentation assume there's already a PresentationConnection w3c/presentation-api#366 (1 comment by @markafoltz)
-
Clarify arguments to getting presentation displays availability information w3c/presentation-api#363 (1 comment by @markafoltz)
-
setConnection in example 5.5 may put UI in an inconsistent state w3c/presentation-api#339 (1 comment by @markafoltz)
-
-
10 pull requests opened.
-
Clarifies inputs to algorithms. w3c/presentation-api#378, by @markafoltz.
-
Move mixed content check to PresentationRequest ctor. w3c/presentation-api#377, by @markafoltz.
-
Clarify identities of PresentationConnection objects in reconnect() steps w3c/presentation-api#376, by @markafoltz.
-
Remove [SameObject] from navigator.presentation.receiver w3c/presentation-api#375, by @markafoltz.
-
Clarify when a simultaneous call to start() can be rejected. w3c/presentation-api#373, by @markafoltz.
-
Replace DOMString with USVString for PresentationRequest URLs. w3c/presentation-api#372, by @markafoltz.
-
Clarify the task source for the specification. w3c/presentation-api#371, by @markafoltz.
-
Clarifies the roles of objects for getting presentation display availability. w3c/presentation-api#370, by @markafoltz.
-
Adds steps for initiating presentation from default presentation request. w3c/presentation-api#369, by @markafoltz.
-
A couple of small fixes to the example code w3c/presentation-api#368, by @markafoltz.
-
-
10 pull requests merged.
-
Clarifies inputs to algorithms. w3c/presentation-api#378.
-
Move mixed content check to PresentationRequest ctor. w3c/presentation-api#377.
-
Clarify when a simultaneous call to start() can be rejected. w3c/presentation-api#373.
-
Clarify the task source for the specification. w3c/presentation-api#371.
-
Clarifies the roles of objects for getting presentation display availability. w3c/presentation-api#370.
-
Remove [SameObject] from navigator.presentation.receiver w3c/presentation-api#375.
-
Adds steps for initiating presentation from default presentation request. w3c/presentation-api#369.
-
Replace DOMString with USVString for PresentationRequest URLs. w3c/presentation-api#372.
-
Clarify identities of PresentationConnection objects in reconnect() steps w3c/presentation-api#376.
-
A couple of small fixes to the example code w3c/presentation-api#368.
-
-
9 pull requests received 46 new comments.
-
Clarifies the roles of objects for getting presentation display availability. w3c/presentation-api#370 (17 comments by @markafoltz, @tidoust)
-
Adds steps for initiating presentation from default presentation request. w3c/presentation-api#369 (14 comments by @markafoltz, @schien, @tidoust)
-
Replace DOMString with USVString for PresentationRequest URLs. w3c/presentation-api#372 (5 comments by @annevk, @markafoltz)
-
Move mixed content check to PresentationRequest ctor. w3c/presentation-api#377 (3 comments by @markafoltz, @mounirlamouri, @tidoust)
-
Remove [SameObject] from navigator.presentation.receiver w3c/presentation-api#375 (2 comments by @markafoltz)
-
Clarify the task source for the specification. w3c/presentation-api#371 (2 comments by @markafoltz, @tidoust)
-
Clarify identities of PresentationConnection objects in reconnect() steps w3c/presentation-api#376 (1 comment by @tidoust)
-
Clarify when a simultaneous call to start() can be rejected. w3c/presentation-api#373 (1 comment by @markafoltz)
-
w3c/remote-playback
-
6 issues opened.
-
Use [SameObject] for HTMLMediaElement#remote w3c/remote-playback#68, by @foolip.
-
Evaluate Security and Privacy impacts w3c/remote-playback#67, by @tidoust.
-
Internationalization considerations w3c/remote-playback#66, by @tidoust.
-
Make NotFoundError when prompt() is called and availability monitoring is not available optional w3c/remote-playback#65, by @avayvod.
-
Merge steps 5 and 9 for prompt() algorithm w3c/remote-playback#64, by @avayvod.
-
prompt() should not be rejected if the state was connected when called w3c/remote-playback#63, by @mounirlamouri.
-
-
7 issues closed.
-
Evaluate Security and Privacy impacts w3c/remote-playback#67.
-
prompt() should not be rejected if the state was connected when called w3c/remote-playback#63.
-
Define interaction with setMediaKeys() / Encrypted Media Extensions w3c/remote-playback#55.
-
Make NotFoundError when prompt() is called and availability monitoring is not available optional w3c/remote-playback#65.
-
Use [SameObject] for HTMLMediaElement#remote w3c/remote-playback#68.
-
Update status section w3c/remote-playback#58.
-
Getting availability and monitoring list of devices algorithms w3c/remote-playback#59.
-
-
8 issues received 24 new comments.
-
Define what should happen when device gets disconnected while playing w3c/remote-playback#56 (6 comments by @avayvod, @mounirlamouri)
-
Make NotFoundError when prompt() is called and availability monitoring is not available optional w3c/remote-playback#65 (5 comments by @avayvod, @markafoltz, @mounirlamouri)
-
Merge steps 5 and 9 for prompt() algorithm w3c/remote-playback#64 (4 comments by @avayvod, @markafoltz, @mounirlamouri)
-
Evaluate Security and Privacy impacts w3c/remote-playback#67 (2 comments by @avayvod, @mounirlamouri)
-
prompt() should not be rejected if the state was connected when called w3c/remote-playback#63 (2 comments by @avayvod, @mounirlamouri)
-
Define interaction with setMediaKeys() / Encrypted Media Extensions w3c/remote-playback#55 (1 comment by @mounirlamouri)
-
Getting availability and monitoring list of devices algorithms w3c/remote-playback#59 (1 comment by @avayvod)
-
-
4 pull requests opened.
-
Add a privacy and security section w3c/remote-playback#69, by @avayvod.
-
Add a section about browser initiated remote playback w3c/remote-playback#62, by @avayvod.
-
SOTD updates to note stability and call for wide review (#58) w3c/remote-playback#61, by @tidoust.
-
Clarify availability monitoring w3c/remote-playback#60, by @avayvod.
-
-
4 pull requests merged.
-
Add a privacy and security section w3c/remote-playback#69.
-
Add a section about browser initiated remote playback w3c/remote-playback#62.
-
Clarify availability monitoring w3c/remote-playback#60.
-
SOTD updates to note stability and call for wide review (#58) w3c/remote-playback#61.
-
-
4 pull requests received 13 new comments.
-
Add a section about browser initiated remote playback w3c/remote-playback#62 (5 comments by @anssiko, @avayvod, @foolip, @mounirlamouri, @tidoust)
-
Clarify availability monitoring w3c/remote-playback#60 (3 comments by @avayvod, @markafoltz, @mounirlamouri)
-
SOTD updates to note stability and call for wide review (#58) w3c/remote-playback#61 (3 comments by @anssiko, @avayvod)
-
w3c/openscreenprotocol
-
13 issues opened.
-
[Meta] Propose security mechanisms for Open Screen protocol w3c/openscreenprotocol#13, by @markafoltz.
-
[Control Protocol] Remote Playback API control protocol w3c/openscreenprotocol#12, by @markafoltz.
-
Presentation API control protocol w3c/openscreenprotocol#11, by @markafoltz.
-
Evaluate Mozilla proposal as a protocol transport w3c/openscreenprotocol#10, by @markafoltz.
-
Evaluate QUIC as a protocol transport w3c/openscreenprotocol#9, by @markafoltz.
-
[Meta] Evaluate protocol transport mechanisms w3c/openscreenprotocol#8, by @markafoltz.
-
Evaluate SSDP/DIAL as a discovery mechanism w3c/openscreenprotocol#7, by @markafoltz.
-
Evaluate Multicast DNS/DNS-SD as a discovery mechanism w3c/openscreenprotocol#6, by @markafoltz.
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5, by @markafoltz.
-
Non-functional requirements w3c/openscreenprotocol#4, by @markafoltz.
-
Requirements: Remote Playback API w3c/openscreenprotocol#3, by @markafoltz.
-
Requirements: Presentation API w3c/openscreenprotocol#2, by @markafoltz.
-
[Meta] Write document describing protocol requirements w3c/openscreenprotocol#1, by @markafoltz.
-
-
5 issues received 6 new comments.
-
[Meta] Evaluate presentation screen discovery mechanisms w3c/openscreenprotocol#5 (2 comments by @louaybassbouss, @markafoltz)
-
[Control Protocol] Remote Playback API control protocol w3c/openscreenprotocol#12 (1 comment by @markafoltz)
-
GitHub
w3c/remote-playback
-
7 issues opened.
-
Getting availability and monitoring list of devices algorithms w3c/remote-playback#59, by @markafoltz.
-
Update status section w3c/remote-playback#58, by @anssiko.
-
Consistency with Presentation API w3c/remote-playback#57, by @chrisn.
-
Define what should happen when device gets disconnected while playing w3c/remote-playback#56, by @mounirlamouri.
-
Define interaction with setMediaKeys() / Encrypted Media Extensions w3c/remote-playback#55, by @markafoltz.
-
Race between cancelWatchAvailability and disableRemotePlayback w3c/remote-playback#53, by @mounirlamouri.
-
cancelWatchAvailability isn't clickable w3c/remote-playback#52, by @mounirlamouri.
-
-
3 issues closed.
-
Consistency with Presentation API w3c/remote-playback#57.
-
Race between cancelWatchAvailability and disableRemotePlayback w3c/remote-playback#53.
-
cancelWatchAvailability isn't clickable w3c/remote-playback#52.
-
-
4 issues received 10 new comments.
-
Consistency with Presentation API w3c/remote-playback#57 (6 comments by @chrisn, @markafoltz, @mounirlamouri, @tidoust)
-
Race between cancelWatchAvailability and disableRemotePlayback w3c/remote-playback#53 (2 comments by @avayvod, @mounirlamouri)
-
Define what should happen when device gets disconnected while playing w3c/remote-playback#56 (1 comment by @mounirlamouri)
-
Define interaction with setMediaKeys() / Encrypted Media Extensions w3c/remote-playback#55 (1 comment by @avayvod)
-
-
1 pull request opened.
-
Clear the set of availability callbacks... w3c/remote-playback#54, by @avayvod.
-
-
1 pull request merged.
-
Clear the set of availability callbacks... w3c/remote-playback#54.
-
-
1 pull request received 3 new comments.
-
Clear the set of availability callbacks... w3c/remote-playback#54 (3 comments by @avayvod, @mounirlamouri)
-
w3c/presentation-api
-
5 issues opened.
-
Clarify arguments to getting presentation displays availability information w3c/presentation-api#363, by @markafoltz.
-
Consider checking for security context in the PresentationRequest constructor w3c/presentation-api#362, by @markafoltz.
-
Use USVString for URLs w3c/presentation-api#361, by @annevk.
-
Clarify event order when establishing a presentation connection w3c/presentation-api#360, by @markafoltz.
-
"setting presentation.defaultRequest will have no effect" note is ambiguous w3c/presentation-api#359, by @tidoust.
-
-
9 issues closed.
-
Presentation display availability is not clearly defined w3c/presentation-api#342.
-
PresentationRequest constructor uses entry settings object, but it probably shouldn't w3c/presentation-api#336.
-
Establishing a presentation connection steps do not handle failures w3c/presentation-api#343.
-
Clarify presentation ID generation requirements w3c/presentation-api#346.
-
navigator.presentation is marked optional in WebIDL w3c/presentation-api#341.
-
Example 5.6 doesn't need onconnect handler w3c/presentation-api#340.
-
PresentationConnectionList is not required for receiving user agents w3c/presentation-api#337.
-
Define that "TV" should appear as token for UA-string when presentation API is used to render on TV w3c/presentation-api#303.
-
Spec for PresentationConnectionCloseEvent closeMessage conflicts with note w3c/presentation-api#344.
-
-
2 issues received 7 new comments.
-
Consider checking for security context in the PresentationRequest constructor w3c/presentation-api#362 (5 comments by @annevk, @markafoltz, @mounirlamouri, @schien)
-
"setting presentation.defaultRequest will have no effect" note is ambiguous w3c/presentation-api#359 (2 comments by @markafoltz)
-
-
10 pull requests merged.
-
Fix example 5.5 and move to ECMAScript2015 w3c/presentation-api#358.
-
Addresses Issue #342: Update definition of available presentation display. w3c/presentation-api#355.
-
Use current settings object in steps that require a settings object. w3c/presentation-api#357.
-
Add error handling to establish a presentation connection algorithm. w3c/presentation-api#356.
-
Addresses Issue #346 w3c/presentation-api#354.
-
Addresses Issue #341 w3c/presentation-api#353.
-
Addresses Issue #340 w3c/presentation-api#352.
-
Implements proposed resolution for Issue #337 w3c/presentation-api#351.
-
Implements proposed resolution for Issue #303 w3c/presentation-api#350.
-
Implements proposed resolution for Issue #344. w3c/presentation-api#349.
-
-
1 pull request received 8 new comments.
-
Fix example 5.5 and move to ECMAScript2015 w3c/presentation-api#358 (8 comments by @kenchris, @markafoltz)
-
GitHub
w3c/presentation-api
-
13 issues opened.
-
Presentation display capability detection w3c/presentation-api#348, by @markafoltz.
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347, by @markafoltz.
-
Clarify presentation ID generation requirements w3c/presentation-api#346, by @markafoltz.
-
Introduction could use some copy editing w3c/presentation-api#345, by @markafoltz.
-
Spec for PresentationConnectionCloseEvent closeMessage conflicts with note w3c/presentation-api#344, by @markafoltz.
-
Establishing a presentation connection steps do not handle failures w3c/presentation-api#343, by @markafoltz.
-
Presentation display availability is not clearly defined w3c/presentation-api#342, by @markafoltz.
-
navigator.presentation is marked optional in WebIDL w3c/presentation-api#341, by @markafoltz.
-
Example 5.6 doesn't need onconnect handler w3c/presentation-api#340, by @markafoltz.
-
setConnection in example 5.5 may put UI in an inconsistent state w3c/presentation-api#339, by @markafoltz.
-
Can the same browsing context act as a controller and receiver? w3c/presentation-api#338, by @markafoltz.
-
PresentationConnectionList is not required for receiving user agents w3c/presentation-api#337, by @markafoltz.
-
PresentationRequest constructor uses entry settings object, but it probably shouldn't w3c/presentation-api#336, by @smaug----.
-
-
19 issues received 26 new comments.
-
PresentationRequest constructor uses entry settings object, but it probably shouldn't w3c/presentation-api#336 (4 comments by @domenic, @markafoltz, @tidoust)
-
Presentation display capability detection w3c/presentation-api#348 (3 comments by @markafoltz, @mounirlamouri, @tidoust)
-
define the behavior for consecutive |getAvailability| w3c/presentation-api#335 (2 comments by @markafoltz, @tidoust)
-
setConnection in example 5.5 may put UI in an inconsistent state w3c/presentation-api#339 (2 comments by @kenchris, @tidoust)
-
Can the same browsing context act as a controller and receiver? w3c/presentation-api#338 (1 comment by @tidoust)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (1 comment by @tidoust)
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (1 comment by @tidoust)
-
Add facility for the opening page to add cloud paired screens as presentation targets w3c/presentation-api#61 (1 comment by @tidoust)
-
Define that "TV" should appear as token for UA-string when presentation API is used to render on TV w3c/presentation-api#303 (1 comment by @tidoust)
-
PresentationConnectionList is not required for receiving user agents w3c/presentation-api#337 (1 comment by @tidoust)
-
navigator.presentation is marked optional in WebIDL w3c/presentation-api#341 (1 comment by @tidoust)
-
Presentation display availability is not clearly defined w3c/presentation-api#342 (1 comment by @tidoust)
-
Establishing a presentation connection steps do not handle failures w3c/presentation-api#343 (1 comment by @tidoust)
-
Spec for PresentationConnectionCloseEvent closeMessage conflicts with note w3c/presentation-api#344 (1 comment by @tidoust)
-
[Streams] Prototype a Streams API compatible PresentationConnection w3c/presentation-api#282 (1 comment by @markafoltz)
-
-
10 pull requests opened.
-
Fix example 5.5 and move to ECMAScript2015 w3c/presentation-api#358, by @kenchris.
-
Use current settings object in steps that require a settings object. w3c/presentation-api#357, by @markafoltz.
-
Add error handling to establish a presentation connection algorithm. w3c/presentation-api#356, by @markafoltz.
-
Addresses Issue #342: Update definition of available presentation display. w3c/presentation-api#355, by @markafoltz.
-
Addresses Issue #346 w3c/presentation-api#354, by @markafoltz.
-
Addresses Issue #341 w3c/presentation-api#353, by @markafoltz.
-
Addresses Issue #340 w3c/presentation-api#352, by @markafoltz.
-
Implements proposed resolution for Issue #337 w3c/presentation-api#351, by @markafoltz.
-
Implements proposed resolution for Issue #303 w3c/presentation-api#350, by @markafoltz.
-
Implements proposed resolution for Issue #344. w3c/presentation-api#349, by @markafoltz.
-
-
8 pull requests received 13 new comments.
-
Use current settings object in steps that require a settings object. w3c/presentation-api#357 (5 comments by @domenic, @markafoltz)
-
Addresses Issue #342: Update definition of available presentation display. w3c/presentation-api#355 (2 comments by @markafoltz, @tidoust)
-
w3c/remote-playback
-
3 issues received 14 new comments.
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (12 comments by @avayvod, @foolip, @tidoust)
-
Implementation guidance for browsers when a media element with controls is remoted w3c/remote-playback#48 (1 comment by @tidoust)
-
GitHub
w3c/presentation-api
-
3 issues opened.
-
define the behavior for consecutive |getAvailability| w3c/presentation-api#335, by @schien.
-
specify the prohibits mixed security contexts algorithm for multiple presentation URLs w3c/presentation-api#329, by @schien.
-
DOMString[] is not valid Web IDL w3c/presentation-api#328, by @domenic.
-
-
7 issues closed.
-
list of displays: should it address display name, language, etc.? w3c/presentation-api#315.
-
specify the prohibits mixed security contexts algorithm for multiple presentation URLs w3c/presentation-api#329.
-
PresentationConnection.url should be optional? w3c/presentation-api#325.
-
"SHOULD act as if " is unclear w3c/presentation-api#323.
-
PresentationConnectionClosedEvent should be PresentationConnectionCloseEvent w3c/presentation-api#324.
-
Behavior of new PresentationRequest([]) should be defined w3c/presentation-api#327.
-
DOMString[] is not valid Web IDL w3c/presentation-api#328.
-
-
4 issues received 5 new comments.
-
specify the prohibits mixed security contexts algorithm for multiple presentation URLs w3c/presentation-api#329 (2 comments by @markafoltz, @schien)
-
list of displays: should it address display name, language, etc.? w3c/presentation-api#315 (1 comment by @markafoltz)
-
-
5 pull requests opened.
-
Clarify the default presentation request mechanism? w3c/presentation-api#334, by @tidoust.
-
Adds an implementation note for advertising and rendering a user friendly display name w3c/presentation-api#333, by @markafoltz.
-
Make PresentationConnection.id mandatory. w3c/presentation-api#332, by @markafoltz.
-
Update security check step to handle multiple URLs. w3c/presentation-api#331, by @markafoltz.
-
Some editorial fixes suggested by GitHub issues w3c/presentation-api#330, by @markafoltz.
-
-
6 pull requests merged.
-
Clarify the default presentation request mechanism? w3c/presentation-api#334.
-
Adds an implementation note for advertising and rendering a user friendly display name w3c/presentation-api#333.
-
Fix typo in code for Example 7. w3c/presentation-api#326.
-
Update security check step to handle multiple URLs. w3c/presentation-api#331.
-
Make PresentationConnection.id mandatory. w3c/presentation-api#332.
-
Some editorial fixes suggested by GitHub issues w3c/presentation-api#330.
-
-
6 pull requests received 12 new comments.
-
Clarify the default presentation request mechanism? w3c/presentation-api#334 (6 comments by @markafoltz, @tidoust)
-
Adds an implementation note for advertising and rendering a user friendly display name w3c/presentation-api#333 (2 comments by @tidoust, @tomoyukilabs)
-
TR publications
-
2 documents published.
-
Presentation API published as a Candidate Recommendation Snapshot. History of Presentation API
-
Remote Playback API published as a First Public Working Draft. History of Remote Playback API
-
Participants
-
1 organization joined.
-
Alibaba Group joined.
-
GitHub
w3c/presentation-api
-
4 issues opened.
-
Behavior of new PresentationRequest([]) should be defined w3c/presentation-api#327, by @markafoltz.
-
PresentationConnection.url should be optional? w3c/presentation-api#325, by @markafoltz.
-
PresentationConnectionClosedEvent should be PresentationConnectionCloseEvent w3c/presentation-api#324, by @markafoltz.
-
"SHOULD act as if " is unclear w3c/presentation-api#323, by @smaug----.
-
-
2 issues closed.
-
[meta] Publish Candidate Recommendation w3c/presentation-api#276.
-
Clear service worker's persistent storages in a receiving browsing context w3c/presentation-api#318.
-
-
4 issues received 12 new comments.
-
[meta] Publish Candidate Recommendation w3c/presentation-api#276 (6 comments by @anssiko, @markafoltz, @tidoust)
-
[meta] Presentation API Testing w3c/presentation-api#266 (4 comments by @anssiko, @louaybassbouss, @markafoltz)
-
-
3 pull requests opened.
-
Fix typo in code for Example 7. w3c/presentation-api#326, by @lauweijie.
-
Updated SoTD for publication as Candidate Recommendation w3c/presentation-api#322, by @tidoust.
-
Missing interface terms and reference to DOM standard added w3c/presentation-api#321, by @tidoust.
-
-
3 pull requests merged.
-
Updated SoTD for publication as Candidate Recommendation w3c/presentation-api#322.
-
Missing interface terms and reference to DOM standard added w3c/presentation-api#321.
-
Addresses Issue #318 w3c/presentation-api#320.
-
-
3 pull requests received 6 new comments.
-
Missing interface terms and reference to DOM standard added w3c/presentation-api#321 (3 comments by @anssiko, @markafoltz, @tidoust)
-
Updated SoTD for publication as Candidate Recommendation w3c/presentation-api#322 (2 comments by @anssiko, @markafoltz)
-
w3c/remote-playback
-
8 issues closed.
-
[meta] Publish First Public Working Draft w3c/remote-playback#12.
-
Allow websites to stop the remote playback w3c/remote-playback#4.
-
Allow the user agent to choose which media element source to play remotely w3c/remote-playback#7.
-
Specify the transition between the local and remote playback when changing remote.state w3c/remote-playback#25.
-
Do we need remote.getAvailability()? w3c/remote-playback#39.
-
Change connect() to return Promise<void> w3c/remote-playback#45.
-
Need to define behavior of media.remote when disableRemotePlayback = true w3c/remote-playback#47.
-
-
10 issues received 18 new comments.
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46 (5 comments by @avayvod, @foolip, @mounirlamouri)
-
Allow the user agent to choose which media element source to play remotely w3c/remote-playback#7 (4 comments by @avayvod, @foolip)
-
Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback w3c/remote-playback#6 (1 comment by @avayvod)
-
Specify the transition between the local and remote playback when changing remote.state w3c/remote-playback#25 (1 comment by @avayvod)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (1 comment by @avayvod)
-
Need to define behavior of media.remote when disableRemotePlayback = true w3c/remote-playback#47 (1 comment by @avayvod)
-
-
3 pull requests opened.
-
Adds customized paragraph to SoTD that mentions the Presentation API w3c/remote-playback#50, by @tidoust.
-
Prepare the spec for the First Public Working Draft by addressing existing issues w3c/remote-playback#49, by @avayvod.
-
3 pull requests merged.
-
Fix typos w3c/remote-playback#51.
-
Prepare the spec for the First Public Working Draft by addressing existing issues w3c/remote-playback#49.
-
Adds customized paragraph to SoTD that mentions the Presentation API w3c/remote-playback#50.
-
-
3 pull requests received 13 new comments.
-
Prepare the spec for the First Public Working Draft by addressing existing issues w3c/remote-playback#49 (11 comments by @anssiko, @avayvod, @eric-carlson, @mounirlamouri)
-
Adds customized paragraph to SoTD that mentions the Presentation API w3c/remote-playback#50 (1 comment by @anssiko)
-
GitHub
w3c/remote-playback
-
4 issues opened.
-
Implementation guidance for browsers when a media element with controls is remoted w3c/remote-playback#48, by @markafoltz.
-
Need to define behavior of media.remote when disableRemotePlayback = true w3c/remote-playback#47, by @markafoltz.
-
Should rendering behavior of the remote-d media element be specified? w3c/remote-playback#46, by @markafoltz.
-
Change connect() to return Promise<void> w3c/remote-playback#45, by @avayvod.
-
-
6 issues closed.
-
remote.onstatechange vs. remote.on{connect,connecting,disconnect} w3c/remote-playback#36.
-
connect: NotFoundError and NotSupportedError inconsistencies w3c/remote-playback#34.
-
connect: step 3 should probably be a MAY w3c/remote-playback#35.
-
Check initial value of remote.state before starting "Initiate remote playback" w3c/remote-playback#37.
-
Define behavior when "Establishing a connection with a remote playback device" fails w3c/remote-playback#38.
-
setupRemotePlayback() called twice in Example 2 and Example 3? w3c/remote-playback#40.
-
-
9 issues received 34 new comments.
-
[meta] Publish First Public Working Draft w3c/remote-playback#12 (10 comments by @anssiko, @avayvod, @foolip, @tidoust)
-
Specify the transition between the local and remote playback when changing remote.state w3c/remote-playback#25 (7 comments by @avayvod, @foolip, @mounirlamouri)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (6 comments by @avayvod, @foolip, @markafoltz, @zcorpan)
-
setupRemotePlayback() called twice in Example 2 and Example 3? w3c/remote-playback#40 (1 comment by @avayvod)
-
Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback w3c/remote-playback#6 (1 comment by @foolip)
-
Allow the user agent to choose which media element source to play remotely w3c/remote-playback#7 (1 comment by @foolip)
-
-
3 pull requests opened.
-
Split the statechange event into three, one per state w3c/remote-playback#44, by @avayvod.
-
Fix issues 38, 37, 35 and 34 w3c/remote-playback#43, by @avayvod.
-
Implement swithToLocal/RemoteUI. w3c/remote-playback#42, by @avayvod.
-
-
3 pull requests merged.
-
Split the statechange event into three, one per state w3c/remote-playback#44.
-
Fix issues 38, 37, 35 and 34 w3c/remote-playback#43.
-
Implement swithToLocal/RemoteUI. w3c/remote-playback#42.
-
-
1 pull request received 1 new comment.
w3c/presentation-api
-
3 issues opened.
-
Clear service worker's persistent storages in a receiving browsing context w3c/presentation-api#318, by @anssiko.
-
list of displays: should it address display name, language, etc.? w3c/presentation-api#315, by @aphillips.
-
mismatch onconnectionavailable handling for receiver in sample code w3c/presentation-api#313, by @schien.
-
-
8 issues closed.
-
Add presentation request URL fallback mechanism w3c/presentation-api#311.
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153.
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99.
-
defaultRequest text should explicitely mentions iframes that have presentation disabled from sandboxing w3c/presentation-api#293.
-
mismatch onconnectionavailable handling for receiver in sample code w3c/presentation-api#313.
-
Wrong algorithm reference for terminating a presentation in a receiving browsing context w3c/presentation-api#309.
-
User Data Controls in Web Browsers guidelines w3c/presentation-api#275.
-
Move sandbox flag to HTML spec w3c/presentation-api#299.
-
-
10 issues received 36 new comments.
-
[meta] Presentation API Testing w3c/presentation-api#266 (7 comments by @anssiko, @Honry, @louaybassbouss, @zqzhang)
-
Define that "TV" should appear as token for UA-string when presentation API is used to render on TV w3c/presentation-api#303 (5 comments by @anawhj, @markafoltz, @tidoust, @tomoyukilabs)
-
list of displays: should it address display name, language, etc.? w3c/presentation-api#315 (5 comments by @aphillips, @tidoust, @tomoyukilabs)
-
Clear service worker's persistent storages in a receiving browsing context w3c/presentation-api#318 (3 comments by @anssiko, @tomoyukilabs)
-
Add presentation request URL fallback mechanism w3c/presentation-api#311 (3 comments by @anssiko, @markafoltz)
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99 (3 comments by @anssiko, @markafoltz)
-
User Data Controls in Web Browsers guidelines w3c/presentation-api#275 (3 comments by @anssiko, @markafoltz)
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153 (1 comment by @anssiko)
-
defaultRequest text should explicitely mentions iframes that have presentation disabled from sandboxing w3c/presentation-api#293 (1 comment by @markafoltz)
-
-
5 pull requests opened.
-
Addresses Issue #318 w3c/presentation-api#320, by @tomoyukilabs.
-
Fix typos raised by @schien w3c/presentation-api#319, by @tidoust.
-
Updates PR #310 w3c/presentation-api#317, by @markafoltz.
-
Updates PresentationRequest to take multiple URLs w3c/presentation-api#316, by @markafoltz.
-
CR Exit criteria w3c/presentation-api#314, by @tidoust.
-
-
8 pull requests merged.
-
Updates PresentationRequest to take multiple URLs w3c/presentation-api#316.
-
Ignore defaultRequest if presentation disabled by sandbox flag. w3c/presentation-api#310.
-
Updates PR #310 w3c/presentation-api#317.
-
Fix typos raised by @schien w3c/presentation-api#319.
-
Partially addresses Issue 275 w3c/presentation-api#308.
-
CR Exit criteria w3c/presentation-api#314.
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#305.
-
Fix typo in code for Example 6. w3c/presentation-api#312.
-
-
8 pull requests received 29 new comments.
-
Updates PresentationRequest to take multiple URLs w3c/presentation-api#316 (14 comments by @anssiko, @markafoltz, @mounirlamouri, @tidoust)
-
Partially addresses Issue 275 w3c/presentation-api#308 (6 comments by @anssiko, @markafoltz, @tidoust)
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#305 (2 comments by @anssiko, @mounirlamouri)
-
Ignore defaultRequest if presentation disabled by sandbox flag. w3c/presentation-api#310 (1 comment by @anssiko)
-
TR publications
-
1 document published.
-
Presentation API published as a Working Draft. History of Presentation API
-
Participants
-
1 organization joined.
-
VIGOUR joined.
-
GitHub
w3c/presentation-api
-
8 issues opened.
-
Add presentation request URL fallback mechanism w3c/presentation-api#311, by @anssiko.
-
Wrong algorithm reference for terminating a presentation in a receiving browsing context w3c/presentation-api#309, by @schien.
-
Define that "TV" should appear as token for UA-string when presentation API is used to render on TV w3c/presentation-api#303, by @sicking.
-
Update acknowledgments w3c/presentation-api#301, by @anssiko.
-
Move sandbox flag to HTML spec w3c/presentation-api#299, by @mounirlamouri.
-
Check references category and stability w3c/presentation-api#295, by @tidoust.
-
defaultRequest text should explicitely mentions iframes that have presentation disabled from sandboxing w3c/presentation-api#293, by @mounirlamouri.
-
[meta] Publish a new Working Draft before the F2F - review the latest ED by 9 May w3c/presentation-api#289, by @anssiko.
-
-
9 issues closed.
-
GitHub API failing, which leads to ReSpec failures w3c/presentation-api#228.
-
Describe the use cases for terminate vs close w3c/presentation-api#242.
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255.
-
Update acknowledgments w3c/presentation-api#301.
-
define error handling if fail to establish presentation connection on receiving UA w3c/presentation-api#283.
-
Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes w3c/presentation-api#268.
-
travis-cl complains about obsolete nvm version w3c/presentation-api#265.
-
[meta] Publish a new Working Draft before the F2F - review the latest ED by 9 May w3c/presentation-api#289.
-
define the detailed behavior of disable Presentation API in sandbox w3c/presentation-api#288.
-
-
12 issues received 29 new comments.
-
[meta] Publish a new Working Draft before the F2F - review the latest ED by 9 May w3c/presentation-api#289 (4 comments by @anssiko, @markafoltz, @tidoust)
-
User Data Controls in Web Browsers guidelines w3c/presentation-api#275 (3 comments by @mnot, @tidoust)
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99 (3 comments by @anawhj, @markafoltz, @tidoust)
-
define the detailed behavior of disable Presentation API in sandbox w3c/presentation-api#288 (3 comments by @markafoltz, @schien)
-
Describe the use cases for terminate vs close w3c/presentation-api#242 (2 comments by @birtles, @markafoltz)
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255 (2 comments by @markafoltz, @tidoust)
-
define error handling if fail to establish presentation connection on receiving UA w3c/presentation-api#283 (1 comment by @markafoltz)
-
defaultRequest text should explicitely mentions iframes that have presentation disabled from sandboxing w3c/presentation-api#293 (1 comment by @anssiko)
-
16 pull requests opened.
-
Fix typo in code for Example 6. w3c/presentation-api#312, by @lauweijie.
-
Ignore defaultRequest if presentation disabled by sandbox flag. w3c/presentation-api#310, by @mounirlamouri.
-
Partially addresses Issue 275 w3c/presentation-api#308, by @markafoltz.
-
Add requirement and use cases for terminate presentation w3c/presentation-api#307, by @markafoltz.
-
Issue #228: Remove GitHub issue code. w3c/presentation-api#306, by @markafoltz.
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#305, by @markafoltz.
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#304, by @markafoltz.
-
Updated acknowledgements list (#301), marked non-normative sections w3c/presentation-api#302, by @tidoust.
-
add detailed error handling for receiver w3c/presentation-api#300, by @schien.
-
Corrected Stop button ID in example code w3c/presentation-api#298, by @chrisn.
-
Switched to "generic" language in Travis CI to avoid warnings (#265) w3c/presentation-api#297, by @tidoust.
-
Fix link to WebIDL "throw", update ref to WebIDL to target Second Level w3c/presentation-api#296, by @tidoust.
-
fixing typos w3c/presentation-api#294, by @dret.
-
Reject when sandbox blocks the feature instead of not exposing. w3c/presentation-api#292, by @mounirlamouri.
-
Detailed changes since last WD in SOTD w3c/presentation-api#291, by @tidoust.
-
Pass the presentation identifier when starting a presentation. w3c/presentation-api#290, by @markafoltz.
-
-
12 pull requests merged.
-
Add requirement and use cases for terminate presentation w3c/presentation-api#307.
-
Issue #228: Remove GitHub issue code. w3c/presentation-api#306.
-
Updated acknowledgements list (#301), marked non-normative sections w3c/presentation-api#302.
-
add detailed error handling for receiver w3c/presentation-api#300.
-
Corrected Stop button ID in example code w3c/presentation-api#298.
-
Switched to "generic" language in Travis CI to avoid warnings (#265) w3c/presentation-api#297.
-
Fix link to WebIDL "throw", update ref to WebIDL to target Second Level w3c/presentation-api#296.
-
fixing typos w3c/presentation-api#294.
-
Reject when sandbox blocks the feature instead of not exposing. w3c/presentation-api#292.
-
Detailed changes since last WD in SOTD w3c/presentation-api#291.
-
Pass the presentation identifier when starting a presentation. w3c/presentation-api#290.
-
Clarified which UA performs the receiving browsing context step w3c/presentation-api#287.
-
-
1 pull request closed.
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#304.
-
-
15 pull requests received 29 new comments.
-
Reject when sandbox blocks the feature instead of not exposing. w3c/presentation-api#292 (10 comments by @markafoltz, @mounirlamouri)
-
Ignore defaultRequest if presentation disabled by sandbox flag. w3c/presentation-api#310 (3 comments by @markafoltz, @mounirlamouri)
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#305 (2 comments by @markafoltz, @mounirlamouri)
-
Add requirement and use cases for terminate presentation w3c/presentation-api#307 (1 comment by @mounirlamouri)
-
Addresses APIs with user input on receiving user agent (Issue #99) w3c/presentation-api#304 (1 comment by @markafoltz)
-
Updated acknowledgements list (#301), marked non-normative sections w3c/presentation-api#302 (1 comment by @markafoltz)
-
Switched to "generic" language in Travis CI to avoid warnings (#265) w3c/presentation-api#297 (1 comment by @markafoltz)
-
Pass the presentation identifier when starting a presentation. w3c/presentation-api#290 (1 comment by @tidoust)
-
Clarified which UA performs the receiving browsing context step w3c/presentation-api#287 (1 comment by @markafoltz)
-
w3c/remote-playback
-
9 issues opened.
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41, by @markafoltz.
-
setupRemotePlayback() called twice in Example 2 and Example 3? w3c/remote-playback#40, by @markafoltz.
-
Do we need remote.getAvailability()? w3c/remote-playback#39, by @markafoltz.
-
Define behavior when "Establishing a connection with a remote playback device" fails w3c/remote-playback#38, by @markafoltz.
-
Check initial value of remote.state before starting "Initiate remote playback" w3c/remote-playback#37, by @markafoltz.
-
remote.onstatechange vs. remote.on{connect,connecting,disconnect} w3c/remote-playback#36, by @markafoltz.
-
connect: step 3 should probably be a MAY w3c/remote-playback#35, by @mounirlamouri.
-
connect: NotFoundError and NotSupportedError inconsistencies w3c/remote-playback#34, by @mounirlamouri.
-
Specify the transition between the local and remote playback when changing remote.state w3c/remote-playback#25, by @avayvod.
-
-
4 issues closed.
-
RemotePlayback.state should have events corresponding to state changes w3c/remote-playback#2.
-
Add "connecting" to the RemotePlaybackState enum w3c/remote-playback#3.
-
Allow implementations to drop some requests if they can't be remotely played w3c/remote-playback#13.
-
Why not use the Safari API? w3c/remote-playback#1.
-
-
16 issues received 49 new comments.
-
Allow websites to stop the remote playback w3c/remote-playback#4 (11 comments by @avayvod, @hober, @jernoble, @markafoltz, @mounirlamouri, @tidoust)
-
[meta] Publish First Public Working Draft w3c/remote-playback#12 (6 comments by @anssiko, @avayvod, @tidoust)
-
Define the interaction with Media Session w3c/remote-playback#10 (5 comments by @avayvod, @foolip, @mounirlamouri, @tidoust)
-
Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback w3c/remote-playback#6 (5 comments by @avayvod, @jernoble, @mounirlamouri, @tidoust)
-
Do we need remote.getAvailability()? w3c/remote-playback#39 (4 comments by @avayvod, @jernoble, @mounirlamouri, @tidoust)
-
[Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting w3c/remote-playback#41 (3 comments by @avayvod, @markafoltz, @tidoust)
-
Allow the user agent to choose which media element source to play remotely w3c/remote-playback#7 (3 comments by @avayvod, @hober, @tidoust)
-
remote.onstatechange vs. remote.on{connect,connecting,disconnect} w3c/remote-playback#36 (2 comments by @hober, @tidoust)
-
Specify the transition between the local and remote playback when changing remote.state w3c/remote-playback#25 (2 comments by @avayvod, @jernoble)
-
connect: NotFoundError and NotSupportedError inconsistencies w3c/remote-playback#34 (1 comment by @mounirlamouri)
-
RemotePlayback.state should have events corresponding to state changes w3c/remote-playback#2 (1 comment by @avayvod)
-
Allow implementations to drop some requests if they can't be remotely played w3c/remote-playback#13 (1 comment by @avayvod)
-
-
16 pull requests opened.
-
Dependencies/Terminology clean-up. w3c/remote-playback#33, by @mounirlamouri.
-
Updated media commands section to use normative assertions w3c/remote-playback#32, by @tidoust.
-
Fixed terms and interfaces definitions and links w3c/remote-playback#31, by @tidoust.
-
A few very minor editorial changes w3c/remote-playback#30, by @chrisn.
-
Some minor changes to the example code w3c/remote-playback#29, by @chrisn.
-
Fix warnings: promise is a basic type from WebIDl, no need to link. w3c/remote-playback#28, by @mounirlamouri.
-
Adjust styles for official 2016 stylesheet w3c/remote-playback#27, by @tidoust.
-
Added wording for source selection w3c/remote-playback#26, by @avayvod.
-
Added description of "state" and "statechange" w3c/remote-playback#24, by @avayvod.
-
Extracted IDL interfaces and related algorithms to API section w3c/remote-playback#23, by @avayvod.
-
Added algorithm for connect() w3c/remote-playback#22, by @avayvod.
-
Expand the RemotePlaybackAvailability description w3c/remote-playback#21, by @avayvod.
-
Add state change monitoring example. w3c/remote-playback#20, by @avayvod.
-
Add remote.connect() example. w3c/remote-playback#19, by @avayvod.
-
Added an example for monitoring remote state change w3c/remote-playback#18, by @avayvod.
-
Add connect() example. w3c/remote-playback#17, by @avayvod.
-
-
16 pull requests merged.
-
Dependencies/Terminology clean-up. w3c/remote-playback#33.
-
Updated media commands section to use normative assertions w3c/remote-playback#32.
-
Fixed terms and interfaces definitions and links w3c/remote-playback#31.
-
Some minor changes to the example code w3c/remote-playback#29.
-
A few very minor editorial changes w3c/remote-playback#30.
-
Added wording for source selection w3c/remote-playback#26.
-
Adjust styles for official 2016 stylesheet w3c/remote-playback#27.
-
Added description of "state" and "statechange" w3c/remote-playback#24.
-
Extracted IDL interfaces and related algorithms to API section w3c/remote-playback#23.
-
Added algorithm for connect() w3c/remote-playback#22.
-
Expand the RemotePlaybackAvailability description w3c/remote-playback#21.
-
Add state change monitoring example. w3c/remote-playback#20.
-
Add remote.connect() example. w3c/remote-playback#19.
-
Added an example for monitoring remote state change w3c/remote-playback#18.
-
Add connect() example. w3c/remote-playback#17.
-
Add an examples section introduction. w3c/remote-playback#16.
-
-
1 pull request closed.
-
Fix warnings: promise is a basic type from WebIDl, no need to link. w3c/remote-playback#28.
-
-
15 pull requests received 67 new comments.
-
Expand the RemotePlaybackAvailability description w3c/remote-playback#21 (16 comments by @avayvod, @mounirlamouri)
-
Added description of "state" and "statechange" w3c/remote-playback#24 (11 comments by @avayvod, @mounirlamouri)
-
Add an examples section introduction. w3c/remote-playback#16 (9 comments by @avayvod, @mounirlamouri)
-
Extracted IDL interfaces and related algorithms to API section w3c/remote-playback#23 (4 comments by @avayvod, @mounirlamouri)
-
Fix warnings: promise is a basic type from WebIDl, no need to link. w3c/remote-playback#28 (3 comments by @avayvod, @mounirlamouri)
-
Added an example for monitoring remote state change w3c/remote-playback#18 (2 comments by @avayvod, @mounirlamouri)
-
Updated media commands section to use normative assertions w3c/remote-playback#32 (1 comment by @avayvod)
-
Participants
-
1 organization joined.
-
Espial Group Inc. joined.
-
GitHub
w3c/presentation-api
-
8 issues opened.
-
define the detailed behavior of disable Presentation API in sandbox w3c/presentation-api#288, by @schien.
-
clean up description for section 6.7.1 w3c/presentation-api#285, by @schien.
-
define error handling if fail to establish presentation connection on receiving UA w3c/presentation-api#283, by @schien.
-
[Streams] Prototype a Streams API compatible PresentationConnection w3c/presentation-api#282, by @markafoltz.
-
PresentationReceiver.connectionList doesn't return the same object all the time w3c/presentation-api#281, by @schien.
-
Specify the algorithm for generating a presentation identifier w3c/presentation-api#279, by @tidoust.
-
[meta] Publish Candidate Recommendation w3c/presentation-api#276, by @anssiko.
-
User Data Controls in Web Browsers guidelines w3c/presentation-api#275, by @anssiko.
-
-
12 issues closed.
-
clean up description for section 6.7.1 w3c/presentation-api#285.
-
Specify the algorithm for generating a presentation identifier w3c/presentation-api#279.
-
Have the receiving browsing context generate the presentation identifier? w3c/presentation-api#253.
-
PresentationReceiver.connectionList doesn't return the same object all the time w3c/presentation-api#281.
-
PresentationConnectionClosedEventInit.message needs to have a default value w3c/presentation-api#273.
-
Only allow one PresentationAvailability per PresentationRequest w3c/presentation-api#269.
-
When is the first presentation connection created in the receiving browsing context? w3c/presentation-api#254.
-
Possibility for a character to be interpreted differently depending on locale w3c/presentation-api#218.
-
PresentationSession should have stream interfaces! w3c/presentation-api#163.
-
Evaluate Presentation API against the Media Accessibility User Requirements spec w3c/presentation-api#162.
-
bufferedAmount property on PresentationConnection w3c/presentation-api#241.
-
Use NotAllowedError for permission denied instead of AbortError w3c/presentation-api#271.
-
-
18 issues received 43 new comments.
-
define error handling if fail to establish presentation connection on receiving UA w3c/presentation-api#283 (7 comments by @avayvod, @markafoltz, @schien)
-
Possibility for a character to be interpreted differently depending on locale w3c/presentation-api#218 (5 comments by @markafoltz, @tomoyukilabs)
-
Have the receiving browsing context generate the presentation identifier? w3c/presentation-api#253 (4 comments by @markafoltz, @tidoust)
-
bufferedAmount property on PresentationConnection w3c/presentation-api#241 (4 comments by @markafoltz, @tidoust)
-
Specify the algorithm for generating a presentation identifier w3c/presentation-api#279 (3 comments by @markafoltz)
-
PresentationSession should have stream interfaces! w3c/presentation-api#163 (3 comments by @domenic, @markafoltz)
-
Evaluate Presentation API against the Media Accessibility User Requirements spec w3c/presentation-api#162 (3 comments by @anssiko, @tidoust)
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255 (2 comments by @anssiko, @markafoltz)
-
PresentationReceiver.connectionList doesn't return the same object all the time w3c/presentation-api#281 (1 comment by @markafoltz)
-
PresentationConnectionClosedEventInit.message needs to have a default value w3c/presentation-api#273 (1 comment by @markafoltz)
-
Only allow one PresentationAvailability per PresentationRequest w3c/presentation-api#269 (1 comment by @markafoltz)
-
When is the first presentation connection created in the receiving browsing context? w3c/presentation-api#254 (1 comment by @markafoltz)
-
Use NotAllowedError for permission denied instead of AbortError w3c/presentation-api#271 (1 comment by @tidoust)
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99 (1 comment by @annevk)
-
-
6 pull requests opened.
-
Clarified which UA performs the receiving browsing context step w3c/presentation-api#287, by @tidoust.
-
Remove redundant paragraph. w3c/presentation-api#286, by @markafoltz.
-
Establishes the algorithm for generating the presentation id. w3c/presentation-api#284, by @markafoltz.
-
Adds spec language around localization w3c/presentation-api#280, by @markafoltz.
-
Updates to PR #277 that addresses issues #254, #269, #273 w3c/presentation-api#278, by @tidoust.
-
Address issues #254, #269, #273 w3c/presentation-api#277, by @markafoltz.
-
-
5 pull requests merged.
-
Remove redundant paragraph. w3c/presentation-api#286.
-
Establishes the algorithm for generating the presentation id. w3c/presentation-api#284.
-
Address issues #254, #269, #273 w3c/presentation-api#277.
-
Updates to PR #277 that addresses issues #254, #269, #273 w3c/presentation-api#278.
-
Adds spec language around localization w3c/presentation-api#280.
-
-
3 pull requests received 18 new comments.
-
Updates to PR #277 that addresses issues #254, #269, #273 w3c/presentation-api#278 (13 comments by @markafoltz, @tidoust)
-
Adds spec language around localization w3c/presentation-api#280 (4 comments by @markafoltz, @tidoust, @tomoyukilabs)
-
w3c/remote-playback
-
2 issues opened.
-
Allow implementations to drop some requests if they can't be remotely played w3c/remote-playback#13, by @mounirlamouri.
-
[meta] Publish First Public Working Draft w3c/remote-playback#12, by @anssiko.
-
-
3 pull requests opened.
-
Add an examples section introduction. w3c/remote-playback#16, by @avayvod.
-
Add [CEReactions] annotation to disableRemotePlayback w3c/remote-playback#15, by @domenic.
-
Added an introduction section w3c/remote-playback#14, by @avayvod.
-
-
2 pull requests merged.
-
Add [CEReactions] annotation to disableRemotePlayback w3c/remote-playback#15.
-
Added an introduction section w3c/remote-playback#14.
-
-
2 pull requests received 4 new comments.
-
Add [CEReactions] annotation to disableRemotePlayback w3c/remote-playback#15 (2 comments by @domenic, @mounirlamouri)
-
Participants
-
1 organization joined.
-
Viacom inc. joined.
-
GitHub
w3c/presentation-api
-
2 issues opened.
-
PresentationConnectionClosedEventInit.message needs to have a default value w3c/presentation-api#273, by @smaug----.
-
Use NotAllowedError for permission denied instead of AbortError w3c/presentation-api#271, by @tobie.
-
-
1 issue closed.
-
Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#86.
-
-
4 issues received 5 new comments.
-
Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#86 (2 comments by @markafoltz)
-
Use NotAllowedError for permission denied instead of AbortError w3c/presentation-api#271 (1 comment by @mounirlamouri)
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
Addresses Issue 86: Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#274, by @markafoltz.
-
Use NotAllowedError instead of AbortError. w3c/presentation-api#272, by @mounirlamouri.
-
Styles adjusted for new official 2016 stylesheet w3c/presentation-api#270, by @tidoust.
-
-
3 pull requests merged.
-
Addresses Issue 86: Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#274.
-
Use NotAllowedError instead of AbortError. w3c/presentation-api#272.
-
Styles adjusted for new official 2016 stylesheet w3c/presentation-api#270.
-
-
2 pull requests received 2 new comments.
-
Addresses Issue 86: Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#274 (1 comment by @mounirlamouri)
-
w3c/remote-playback
-
2 issues opened.
-
Add onstatechange event complementing HTMLMediaElement.remote.state property w3c/remote-playback#11, by @avayvod.
-
Define the interaction with Media Session w3c/remote-playback#10, by @foolip.
-
-
1 issue closed.
-
Add onstatechange event complementing HTMLMediaElement.remote.state property w3c/remote-playback#11.
-
-
1 issue received 1 new comment.
-
Add onstatechange event complementing HTMLMediaElement.remote.state property w3c/remote-playback#11 (1 comment by @avayvod)
-
-
1 pull request opened.
-
Correct safari 9 release notes link w3c/remote-playback#9, by @thijstriemstra.
-
-
1 pull request merged.
-
Correct safari 9 release notes link w3c/remote-playback#9.
-
-
1 pull request received 1 new comment.
TR publications
-
1 document published.
-
Presentation API published as a Working Draft. History of Presentation API
-
GitHub
w3c/presentation-api
-
9 issues opened.
-
Only allow one PresentationAvailability per PresentationRequest w3c/presentation-api#269, by @markafoltz.
-
Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes w3c/presentation-api#268, by @anssiko.
-
[meta] Presentation API Testing w3c/presentation-api#266, by @anssiko.
-
travis-cl complains about obsolete nvm version w3c/presentation-api#265, by @markafoltz.
-
Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection? w3c/presentation-api#259, by @tidoust.
-
Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect' w3c/presentation-api#256, by @mounirlamouri.
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255, by @markafoltz.
-
When is the first presentation connection created in the receiving browsing context? w3c/presentation-api#254, by @tidoust.
-
Have the receiving browsing context generate the presentation identifier? w3c/presentation-api#253, by @tidoust.
-
-
17 issues closed.
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230.
-
[meta] CfC to publish a new Working Draft w3c/presentation-api#244.
-
Define reconnection for cross-page navigation on presenting user agent w3c/presentation-api#18.
-
Specify whether properties of the Presentation are left undefined w3c/presentation-api#205.
-
Availability URLs versus Presentation URLs w3c/presentation-api#154.
-
Would a "closing" connection state be of any use? w3c/presentation-api#240.
-
Rename 'closed', 'terminated' and 'connected' events to 'close', 'terminate' and 'disconnect' w3c/presentation-api#256.
-
Security and privacy considerations w3c/presentation-api#45.
-
"Known connection" in reconnect() may be linked to another browsing context w3c/presentation-api#245.
-
Need algorithm for establishing a presentation connection when the previous connection(s) were closed w3c/presentation-api#229.
-
Define a "set of presentations" for the receiving context? w3c/presentation-api#193.
-
conflict description for uniquely identifying a presentation session w3c/presentation-api#165.
-
Think more about privacy implications in multi-user scenarios w3c/presentation-api#224.
-
Implementation guideline: users should have a way to know which origin is being presented at any time w3c/presentation-api#223.
-
binaryType attribute's default value and get/set behaviour needs to be specified w3c/presentation-api#211.
-
Presentations from within nested browsing contexts w3c/presentation-api#79.
-
-
3 issues reopened.
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230, by @anssiko.
-
[meta] CfC to publish a new Working Draft w3c/presentation-api#244, by @anssiko.
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230, by @anssiko.
-
-
15 issues received 39 new comments.
-
[meta] CfC to publish a new Working Draft w3c/presentation-api#244 (6 comments by @anssiko, @markafoltz)
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230 (6 comments by @anssiko, @louaybassbouss, @markafoltz, @tidoust)
-
Implementation guideline: users should have a way to know which origin is being presented at any time w3c/presentation-api#223 (6 comments by @markafoltz, @tidoust)
-
Is a new Permission type required for presentation display availability? w3c/presentation-api#255 (3 comments by @anssiko, @markafoltz, @mounirlamouri)
-
Would a "closing" connection state be of any use? w3c/presentation-api#240 (3 comments by @markafoltz, @tidoust)
-
Specify whether properties of the Presentation are left undefined w3c/presentation-api#205 (2 comments by @louaybassbouss, @markafoltz)
-
bufferedAmount property on PresentationConnection w3c/presentation-api#241 (2 comments by @markafoltz, @tidoust)
-
Annotate IDL blocks with idl-controlling-ua and/or idl-receiving-ua classes w3c/presentation-api#268 (1 comment by @louaybassbouss)
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153 (1 comment by @anssiko)
-
Should `reconnect` fire a `connectionavailable` event when it returns an existing presentation connection? w3c/presentation-api#259 (1 comment by @markafoltz)
-
w3c/presentation-api#18 (1 comment by @markafoltz)
-
-
11 pull requests opened.
-
Split interface Presentation IDL into partials w3c/presentation-api#267, by @anssiko.
-
Editorial changes to termination conditions w3c/presentation-api#264, by @anssiko.
-
Clarifies when and how presentations are terminated w3c/presentation-api#263, by @markafoltz.
-
Do not trigger "connectionavailable" on reconnect for same presentation w3c/presentation-api#262, by @tidoust.
-
Clarifies handling of Presentation attributes. w3c/presentation-api#261, by @markafoltz.
-
Updates to SoTD to invite wide review of the document w3c/presentation-api#260, by @tidoust.
-
Drop use of passive form for event names (issue #256) w3c/presentation-api#258, by @tidoust.
-
Complete Security and Privacy section w3c/presentation-api#257, by @anssiko.
-
Split "set of presentations" into controlling/receiving sets w3c/presentation-api#252, by @tidoust.
-
Additional UI guidelines for user agents w3c/presentation-api#251, by @markafoltz.
-
Fix #211: Define binaryType default value and get/set behaviour w3c/presentation-api#250, by @anssiko.
-
-
11 pull requests merged.
-
Split interface Presentation IDL into partials w3c/presentation-api#267.
-
Clarifies when and how presentations are terminated w3c/presentation-api#263.
-
Editorial changes to termination conditions w3c/presentation-api#264.
-
Do not trigger "connectionavailable" on reconnect for same presentation w3c/presentation-api#262.
-
Clarifies handling of Presentation attributes. w3c/presentation-api#261.
-
Drop use of passive form for event names (issue #256) w3c/presentation-api#258.
-
Updates to SoTD to invite wide review of the document w3c/presentation-api#260.
-
Complete Security and Privacy section w3c/presentation-api#257.
-
Split "set of presentations" into controlling/receiving sets w3c/presentation-api#252.
-
Additional UI guidelines for user agents w3c/presentation-api#251.
-
Fix #211: Define binaryType default value and get/set behaviour w3c/presentation-api#250.
-
-
1 pull request closed.
-
Handling of nested browsing contexts. w3c/presentation-api#249.
-
-
1 pull request reopened.
-
Fix #211: Define binaryType default value and get/set behaviour w3c/presentation-api#250, by @markafoltz.
-
-
10 pull requests received 42 new comments.
-
Split "set of presentations" into controlling/receiving sets w3c/presentation-api#252 (21 comments by @markafoltz, @tidoust)
-
Clarifies when and how presentations are terminated w3c/presentation-api#263 (6 comments by @anssiko, @markafoltz, @tidoust)
-
Complete Security and Privacy section w3c/presentation-api#257 (6 comments by @anssiko, @markafoltz)
-
Split interface Presentation IDL into partials w3c/presentation-api#267 (2 comments by @anssiko, @louaybassbouss)
-
Handling of nested browsing contexts. w3c/presentation-api#249 (2 comments by @anssiko, @markafoltz)
-
Do not trigger "connectionavailable" on reconnect for same presentation w3c/presentation-api#262 (1 comment by @markafoltz)
-
Drop use of passive form for event names (issue #256) w3c/presentation-api#258 (1 comment by @markafoltz)
-
Updates to SoTD to invite wide review of the document w3c/presentation-api#260 (1 comment by @anssiko)
-
Fix #211: Define binaryType default value and get/set behaviour w3c/presentation-api#250 (1 comment by @markafoltz)
-
w3c/remote-playback
-
1 issue received 3 new comments.
-
Reconnecting media elements to the playback w3c/remote-playback#5 (3 comments by @avayvod, @jernoble)
-
-
1 pull request opened.
-
Fix markup for promise<boolean> w3c/remote-playback#8, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix markup for promise<boolean> w3c/remote-playback#8.
-
-
1 pull request received 1 new comment.
GitHub
w3c/presentation-api
-
6 issues opened.
-
getAvailability procedure is not specified w3c/presentation-api#246, by @tidoust.
-
"Known connection" in reconnect() may be linked to another browsing context w3c/presentation-api#245, by @tidoust.
-
[meta] CfC to publish a new Working Draft w3c/presentation-api#244, by @anssiko.
-
Describe the use cases for terminate vs close w3c/presentation-api#242, by @birtles.
-
bufferedAmount property on PresentationConnection w3c/presentation-api#241, by @tidoust.
-
Would a "closing" connection state be of any use? w3c/presentation-api#240, by @tidoust.
-
-
8 issues closed.
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80.
-
getAvailability procedure is not specified w3c/presentation-api#246.
-
Screen availability mechanism for multiple sessions w3c/presentation-api#40.
-
Run startSession steps in parallel w3c/presentation-api#148.
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217.
-
Wrong use of "Queue a task" and "in parallel" in algorithms w3c/presentation-api#231.
-
ReSpec fails to process current editor's draft w3c/presentation-api#232.
-
define the behavior while receiver calls connection.terminate() w3c/presentation-api#222.
-
-
1 issue reopened.
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217, by @anssiko.
-
-
15 issues received 33 new comments.
-
Would a "closing" connection state be of any use? w3c/presentation-api#240 (9 comments by @tidoust, @tomoyukilabs)
-
[meta] CfC to publish a new Working Draft w3c/presentation-api#244 (4 comments by @anssiko, @markafoltz, @tidoust)
-
ReSpec fails to process current editor's draft w3c/presentation-api#232 (4 comments by @dontcallmedom, @markafoltz, @mounirlamouri, @tidoust)
-
GitHub API failing, which leads to ReSpec failures w3c/presentation-api#228 (3 comments by @markafoltz, @tidoust)
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80 (2 comments by @markafoltz)
-
getAvailability procedure is not specified w3c/presentation-api#246 (2 comments by @markafoltz, @tidoust)
-
Implementation guideline: users should have a way to know which origin is being presented at any time w3c/presentation-api#223 (1 comment by @markafoltz)
-
w3c/presentation-api#18 (1 comment by @tidoust)
-
Screen availability mechanism for multiple sessions w3c/presentation-api#40 (1 comment by @markafoltz)
-
Evaluate Presentation API against the Media Accessibility User Requirements spec w3c/presentation-api#162 (1 comment by @tidoust)
-
Possibility for a character to be interpreted differently depending on locale w3c/presentation-api#218 (1 comment by @tomoyukilabs)
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217 (1 comment by @anssiko)
-
Wrong use of "Queue a task" and "in parallel" in algorithms w3c/presentation-api#231 (1 comment by @markafoltz)
-
define the behavior while receiver calls connection.terminate() w3c/presentation-api#222 (1 comment by @markafoltz)
-
-
11 pull requests opened.
-
Handling of nested browsing contexts. w3c/presentation-api#249, by @markafoltz.
-
Update security requirements for resolution around mixed content. w3c/presentation-api#248, by @markafoltz.
-
Re-inserted the getAvailability procedure w3c/presentation-api#247, by @tidoust.
-
Added enum and event definitions, <var> for variables, fixed references w3c/presentation-api#243, by @tidoust.
-
Updated version of PR #238 w3c/presentation-api#239, by @markafoltz.
-
Split the "close" algorithm into "closing" and "close" procedures w3c/presentation-api#238, by @tidoust.
-
Make all enum values lowercase for consistency w3c/presentation-api#237, by @anssiko.
-
Fixed use of "fire an event" and "fire a simple event" in the spec w3c/presentation-api#236, by @tidoust.
-
Manual merge of PR #234 w3c/presentation-api#235, by @markafoltz.
-
Algorithms updated to use "queue a task" only when needed w3c/presentation-api#234, by @tidoust.
-
Defines behavior for terminate() in controlling and receiving contexts w3c/presentation-api#233, by @markafoltz.
-
-
10 pull requests merged.
-
Update security requirements for resolution around mixed content. w3c/presentation-api#248.
-
Re-inserted the getAvailability procedure w3c/presentation-api#247.
-
Added enum and event definitions, <var> for variables, fixed references w3c/presentation-api#243.
-
Split the "close" algorithm into "closing" and "close" procedures w3c/presentation-api#238.
-
Updated version of PR #238 w3c/presentation-api#239.
-
Make all enum values lowercase for consistency w3c/presentation-api#237.
-
Fixed use of "fire an event" and "fire a simple event" in the spec w3c/presentation-api#236.
-
Algorithms updated to use "queue a task" only when needed w3c/presentation-api#234.
-
Manual merge of PR #234 w3c/presentation-api#235.
-
Defines behavior for terminate() in controlling and receiving contexts w3c/presentation-api#233.
-
-
2 pull requests reopened.
-
Re-inserted the getAvailability procedure w3c/presentation-api#247, by @markafoltz.
-
Make all enum values lowercase for consistency w3c/presentation-api#237, by @markafoltz.
-
-
8 pull requests received 47 new comments.
-
Algorithms updated to use "queue a task" only when needed w3c/presentation-api#234 (12 comments by @markafoltz, @tidoust)
-
Added enum and event definitions, <var> for variables, fixed references w3c/presentation-api#243 (6 comments by @markafoltz, @tidoust)
-
Split the "close" algorithm into "closing" and "close" procedures w3c/presentation-api#238 (6 comments by @markafoltz)
-
Update security requirements for resolution around mixed content. w3c/presentation-api#248 (5 comments by @markafoltz, @tidoust)
-
Fixed use of "fire an event" and "fire a simple event" in the spec w3c/presentation-api#236 (3 comments by @markafoltz, @tidoust)
w3c/remote-playback
-
6 issues opened.
-
Allow the user agent to choose which media element source to play remotely w3c/remote-playback#7, by @avayvod.
-
Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback w3c/remote-playback#6, by @avayvod.
-
Reconnecting media elements to the playback w3c/remote-playback#5, by @avayvod.
-
Allow websites to stop the remote playback w3c/remote-playback#4, by @avayvod.
-
Add "connecting" to the RemotePlaybackState enum w3c/remote-playback#3, by @avayvod.
-
RemotePlayback.state should have events corresponding to state changes w3c/remote-playback#2, by @avayvod.
-
-
5 issues received 14 new comments.
-
Add "connecting" to the RemotePlaybackState enum w3c/remote-playback#3 (6 comments by @foolip, @mounirlamouri)
-
RemotePlayback.state should have events corresponding to state changes w3c/remote-playback#2 (3 comments by @avayvod, @mounirlamouri)
-
Define the UA behavior when the disableRemotePlayback attribute is added during the remote playback w3c/remote-playback#6 (2 comments by @foolip, @mounirlamouri)
-
Reconnecting media elements to the playback w3c/remote-playback#5 (2 comments by @jernoble, @mounirlamouri)
-