Second Screen Working Group - Activity in 2015
No matches.
Participants
-
1 organization joined.
-
KDDI CORPORATION joined.
-
GitHub
w3c/presentation-api
-
7 issues opened.
-
ReSpec fails to process current editor's draft w3c/presentation-api#232, by @markafoltz.
-
Wrong use of "Queue a task" and "in parallel" in algorithms w3c/presentation-api#231, by @tidoust.
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230, by @louaybassbouss.
-
Need algorithm for establishing a presentation connection when the previous connection(s) were closed w3c/presentation-api#229, by @markafoltz.
-
GitHub API failing, which leads to ReSpec failures w3c/presentation-api#228, by @markafoltz.
-
Think more about privacy implications in multi-user scenarios w3c/presentation-api#224, by @tidoust.
-
Implementation guideline: users should have a way to know which origin is being presented at any time w3c/presentation-api#223, by @tidoust.
-
-
6 issues closed.
-
Provide session lifecycle management for presenting page w3c/presentation-api#92.
-
Spec should clarify the initial presentation connection state w3c/presentation-api#216.
-
Message sending in Example 5 happens too early w3c/presentation-api#198.
-
Define behavior when sending a message to a PresentationSession fails w3c/presentation-api#149.
-
Add a "starting" state to PresentationConnection w3c/presentation-api#214.
-
PresentationReceiver: rename getConnection() and getConnections() w3c/presentation-api#201.
-
-
12 issues received 21 new comments.
-
Add a "starting" state to PresentationConnection w3c/presentation-api#214 (5 comments by @avayvod, @markafoltz, @tidoust)
-
define the behavior while receiver calls connection.terminate() w3c/presentation-api#222 (4 comments by @anssiko, @markafoltz)
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217 (3 comments by @anssiko, @markafoltz)
-
Provide session lifecycle management for presenting page w3c/presentation-api#92 (1 comment by @markafoltz)
-
Spec should clarify the initial presentation connection state w3c/presentation-api#216 (1 comment by @markafoltz)
-
Define behavior when sending a message to a PresentationSession fails w3c/presentation-api#149 (1 comment by @markafoltz)
-
Wrong use of "Queue a task" and "in parallel" in algorithms w3c/presentation-api#231 (1 comment by @markafoltz)
-
Presentation API IDL Tests for Presentation Interface w3c/presentation-api#230 (1 comment by @markafoltz)
-
PresentationReceiver: rename getConnection() and getConnections() w3c/presentation-api#201 (1 comment by @mounirlamouri)
-
Define a "set of presentations" for the receiving context? w3c/presentation-api#193 (1 comment by @markafoltz)
-
-
3 pull requests opened.
-
Adds a new "connecting" state and per-state event handlers. w3c/presentation-api#227, by @markafoltz.
-
Sync example 6 with changes in #221, rename PresentationReceiver.connections to .connectionList w3c/presentation-api#226, by @anssiko.
-
Reorder api w3c/presentation-api#225, by @markafoltz.
-
-
4 pull requests merged.
-
Adds a new "connecting" state and per-state event handlers. w3c/presentation-api#227.
-
Sync example 6 with changes in #221, rename PresentationReceiver.connections to .connectionList w3c/presentation-api#226.
-
Reorder api w3c/presentation-api#225.
-
Update PresentationReceiver spec to match the results from the discussions in #201 w3c/presentation-api#221.
-
-
3 pull requests received 34 new comments.
-
Update PresentationReceiver spec to match the results from the discussions in #201 w3c/presentation-api#221 (23 comments by @markafoltz, @mounirlamouri)
-
Adds a new "connecting" state and per-state event handlers. w3c/presentation-api#227 (9 comments by @avayvod, @markafoltz, @mounirlamouri, @tidoust)
-
Sync example 6 with changes in #221, rename PresentationReceiver.connections to .connectionList w3c/presentation-api#226 (2 comments by @anssiko, @markafoltz)
-
GitHub
w3c/presentation-api
-
4 issues opened.
-
define the behavior while receiver calls connection.terminate() w3c/presentation-api#222, by @schien.
-
CG rechartering w3c/presentation-api#220, by @wayneca.
-
Possibility for a character to be interpreted differently depending on locale w3c/presentation-api#218, by @tidoust.
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217, by @markafoltz.
-
-
4 issues closed.
-
CG rechartering w3c/presentation-api#220.
-
Example 5 has a redundant disconnectController() function w3c/presentation-api#210.
-
Define user agent context for rendering the presentation w3c/presentation-api#14.
-
Presenting the content of an <audio> or <video> element w3c/presentation-api#13.
-
-
2 issues reopened.
-
Presenting the content of an <audio> or <video> element w3c/presentation-api#13, by @anssiko.
-
Presenting the content of an <audio> or <video> element w3c/presentation-api#13, by @anssiko.
-
-
15 issues received 56 new comments.
-
CG rechartering w3c/presentation-api#220 (16 comments by @anssiko, @karim76, @louaybassbouss, @markafoltz, @schien, @tidoust, @wayneca)
-
Possibility for a character to be interpreted differently depending on locale w3c/presentation-api#218 (13 comments by @aphillips, @duerst, @markafoltz, @r12a, @tidoust, @tkanai)
-
Presentations from within nested browsing contexts w3c/presentation-api#79 (5 comments by @anssiko, @markafoltz, @sicking, @tidoust)
-
Add a PresentationConnection.disconnected state for accidental disconnections w3c/presentation-api#217 (4 comments by @markafoltz, @mounirlamouri)
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35 (4 comments by @markafoltz, @sicking)
-
Specify whether properties of the Presentation are left undefined w3c/presentation-api#205 (1 comment by @louaybassbouss)
-
Add a "starting" state to PresentationConnection w3c/presentation-api#214 (1 comment by @mounirlamouri)
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80 (1 comment by @tidoust)
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99 (1 comment by @tidoust)
-
Define behavior when sending a message to a PresentationSession fails w3c/presentation-api#149 (1 comment by @tidoust)
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153 (1 comment by @tidoust)
-
-
2 pull requests opened.
-
Update PresentationReceiver spec to match the results from the discussions in #201 w3c/presentation-api#221, by @mounirlamouri.
-
Adds an algorithm for creating a receiving browsing context w3c/presentation-api#219, by @markafoltz.
-
-
2 pull requests merged.
-
Adds an algorithm for creating a receiving browsing context w3c/presentation-api#219.
-
Drop disconnectController() on EXAMPLE 5. w3c/presentation-api#215.
-
-
2 pull requests received 4 new comments.
-
Update PresentationReceiver spec to match the results from the discussions in #201 w3c/presentation-api#221 (3 comments by @mounirlamouri, @sicking)
-
w3c/remote-playback
-
1 issue opened.
-
Why not use the Safari API? w3c/remote-playback#1, by @sicking.
-
-
1 issue received 8 new comments.
-
Why not use the Safari API? w3c/remote-playback#1 (8 comments by @jernoble, @mounirlamouri, @sicking)
-
TR publications
-
1 document published.
-
Presentation API published as a Working Draft. History of Presentation API
-
Participants
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/presentation-api
-
8 issues opened.
-
Spec should clarify the initial presentation connection state w3c/presentation-api#216, by @tidoust.
-
Add a "starting" state to PresentationConnection w3c/presentation-api#214, by @markafoltz.
-
binaryType attribute's default value and get/set behaviour needs to be specified w3c/presentation-api#211, by @anssiko.
-
Example 5 has a redundant disconnectController() function w3c/presentation-api#210, by @anssiko.
-
Add definition for "presentation" to Common idioms w3c/presentation-api#209, by @anssiko.
-
Specify whether properties of the Presentation are left undefined w3c/presentation-api#205, by @markafoltz.
-
Presentations without communication channel w3c/presentation-api#202, by @tidoust.
-
PresentationReceiver: rename getConnection() and getConnections() w3c/presentation-api#201, by @mounirlamouri.
-
-
10 issues closed.
-
Add definition for "presentation" to Common idioms w3c/presentation-api#209.
-
Event the presentation receiver when the last session has disconnected w3c/presentation-api#194.
-
Convert URL passed to PresentationRequest to an absolute URL w3c/presentation-api#200.
-
Empty ´<head>´ element in Example 4 w3c/presentation-api#199.
-
"reconnect to a presentation session" algorithm has an unclear input w3c/presentation-api#187.
-
Define whether multiple simultaneous calls are permitted to startSession() w3c/presentation-api#21.
-
Update the Status section, note stability per section w3c/presentation-api#112.
-
Conformance classes definition w3c/presentation-api#93.
-
Rename PresentationSession to PresentationController w3c/presentation-api#171.
-
Reconcile sessionavailable vs. sessionconnect for notifying page of session connection w3c/presentation-api#152.
-
-
2 issues reopened.
-
Message sending in Example 5 happens too early w3c/presentation-api#198, by @anssiko.
-
Presenting the content of an <audio> or <video> element w3c/presentation-api#13, by @markafoltz.
-
-
13 issues received 47 new comments.
-
PresentationReceiver: rename getConnection() and getConnections() w3c/presentation-api#201 (29 comments by @avayvod, @markafoltz, @mounirlamouri, @sicking)
-
Reconcile sessionavailable vs. sessionconnect for notifying page of session connection w3c/presentation-api#152 (4 comments by @markafoltz, @mounirlamouri, @tidoust)
-
Add definition for "presentation" to Common idioms w3c/presentation-api#209 (2 comments by @anssiko, @markafoltz)
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67 (2 comments by @louaybassbouss, @tidoust)
-
Event the presentation receiver when the last session has disconnected w3c/presentation-api#194 (1 comment by @markafoltz)
-
Update the Status section, note stability per section w3c/presentation-api#112 (1 comment by @markafoltz)
-
conflict description for uniquely identifying a presentation session w3c/presentation-api#165 (1 comment by @markafoltz)
-
w3c/presentation-api#13 (1 comment by @markafoltz)
-
Evaluate Presentation API against the Media Accessibility User Requirements spec w3c/presentation-api#162 (1 comment by @tidoust)
-
Rename PresentationSession to PresentationController w3c/presentation-api#171 (1 comment by @markafoltz)
-
-
8 pull requests opened.
-
Drop disconnectController() on EXAMPLE 5. w3c/presentation-api#215, by @hyunjunekim.
-
Use concise, contemporary style for exceptions w3c/presentation-api#213, by @anssiko.
-
Editorial changes w3c/presentation-api#212, by @anssiko.
-
Modify some context about terminate. w3c/presentation-api#208, by @hyunjunekim.
-
Change EXAMPLE 6 for title unity. w3c/presentation-api#207, by @prises0221.
-
Small fixes w3c/presentation-api#206, by @markafoltz.
-
Defines two conformance classes for the specification w3c/presentation-api#204, by @markafoltz.
-
Renames PresentationSession to PresentationConnection w3c/presentation-api#203, by @markafoltz.
-
-
7 pull requests merged.
-
Use concise, contemporary style for exceptions w3c/presentation-api#213.
-
Editorial changes w3c/presentation-api#212.
-
Modify some context about terminate. w3c/presentation-api#208.
-
Change EXAMPLE 6 for title unity. w3c/presentation-api#207.
-
Small fixes w3c/presentation-api#206.
-
Defines two conformance classes for the specification w3c/presentation-api#204.
-
Renames PresentationSession to PresentationConnection w3c/presentation-api#203.
-
-
6 pull requests received 30 new comments.
-
Defines two conformance classes for the specification w3c/presentation-api#204 (21 comments by @markafoltz, @tidoust)
-
Renames PresentationSession to PresentationConnection w3c/presentation-api#203 (5 comments by @markafoltz, @mounirlamouri, @tidoust)
-
GitHub
w3c/presentation-api
-
8 issues opened.
-
Convert URL passed to PresentationRequest to an absolute URL w3c/presentation-api#200, by @tidoust.
-
Empty ´<head>´ element in Example 4 w3c/presentation-api#199, by @louaybassbouss.
-
Message sending in Example 5 happens too early w3c/presentation-api#198, by @tidoust.
-
Event the presentation receiver when the last session has disconnected w3c/presentation-api#194, by @markafoltz.
-
Define a "set of presentations" for the receiving context? w3c/presentation-api#193, by @tidoust.
-
"reconnect to a presentation session" algorithm has an unclear input w3c/presentation-api#187, by @anssiko.
-
PresentationSessionConnectEventInit.session should be either [required] or nullable (and default to null) w3c/presentation-api#184, by @smaug----.
-
-
5 issues closed.
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35.
-
Separate interface for controlling page and presenting page w3c/presentation-api#91.
-
Rename join() to something that reflects its intended use better w3c/presentation-api#170.
-
-
18 issues received 58 new comments.
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35 (20 comments by @anssiko, @avayvod, @markafoltz, @mounirlamouri, @schien, @sicking, @tidoust)
-
Separate interface for controlling page and presenting page w3c/presentation-api#91 (8 comments by @anssiko, @mounirlamouri, @schien, @sicking, @tidoust)
-
Security and privacy considerations w3c/presentation-api#45 (5 comments by @anssiko, @markafoltz, @sicking, @tidoust)
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153 (3 comments by @annevk, @tidoust)
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80 (3 comments by @markafoltz, @mwatson2, @tidoust)
-
Rename PresentationSession to PresentationController w3c/presentation-api#171 (3 comments by @avayvod, @markafoltz, @sicking)
-
Event the presentation receiver when the last session has disconnected w3c/presentation-api#194 (2 comments by @anssiko, @sicking)
-
Presentations from within nested browsing contexts w3c/presentation-api#79 (2 comments by @markafoltz, @tidoust)
-
PresentationSession should have stream interfaces! w3c/presentation-api#163 (2 comments by @domenic, @markafoltz)
-
If TV and etc have many browsers, How to select and launch the browser or web-app based on blink, gecko or webkit. w3c/presentation-api#189 (2 comments by @anssiko, @louaybassbouss)
-
Convert URL passed to PresentationRequest to an absolute URL w3c/presentation-api#200 (1 comment by @anssiko)
-
Message sending in Example 5 happens too early w3c/presentation-api#198 (1 comment by @louaybassbouss)
-
w3c/presentation-api#9 (1 comment by @tidoust)
-
w3c/presentation-api#13 (1 comment by @tidoust)
-
Define a "set of presentations" for the receiving context? w3c/presentation-api#193 (1 comment by @markafoltz)
-
Reconcile sessionavailable vs. sessionconnect for notifying page of session connection w3c/presentation-api#152 (1 comment by @markafoltz)
-
PresentationSessionConnectEventInit.session should be either [required] or nullable (and default to null) w3c/presentation-api#184 (1 comment by @mounirlamouri)
-
Rename join() to something that reflects its intended use better w3c/presentation-api#170 (1 comment by @sicking)
-
-
10 pull requests opened.
-
Fix up wrong codes about "EXAMPLE6" w3c/presentation-api#197, by @hyunjunekim.
-
Rename "presenting browsing context" to "receiving browsing context" on "uc-req.md" file. w3c/presentation-api#196, by @hyunjunekim.
-
Fix respec warnings. w3c/presentation-api#195, by @mounirlamouri.
-
Reorder start steps to create session only when needed w3c/presentation-api#192, by @tidoust.
-
Rename "presenting browsing context" to "receiving browsing context". w3c/presentation-api#191, by @mounirlamouri.
-
Adds terminate() to PresentationSession and defines behavior for it. w3c/presentation-api#190, by @markafoltz.
-
Address timeless' editorial feedback w3c/presentation-api#188, by @anssiko.
-
Add PresentationReceiver and navigator.presentation.receiver to access it. w3c/presentation-api#186, by @mounirlamouri.
-
Make session a required argument when constructing a PresentationSessionConnect. w3c/presentation-api#185, by @mounirlamouri.
-
Editorial changes to interoperability document. w3c/presentation-api#183, by @markafoltz.
-
-
12 pull requests merged.
-
Fix up wrong codes about "EXAMPLE6" w3c/presentation-api#197.
-
Rename "presenting browsing context" to "receiving browsing context" on "uc-req.md" file. w3c/presentation-api#196.
-
Fix respec warnings. w3c/presentation-api#195.
-
Rename "presenting browsing context" to "receiving browsing context". w3c/presentation-api#191.
-
Adds terminate() to PresentationSession and defines behavior for it. w3c/presentation-api#190.
-
Reorder start steps to create session only when needed w3c/presentation-api#192.
-
Add PresentationReceiver and navigator.presentation.receiver to access it. w3c/presentation-api#186.
-
Make session a required argument when constructing a PresentationSessionConnect. w3c/presentation-api#185.
-
Address timeless' editorial feedback w3c/presentation-api#188.
-
Editorial: fix the the spec warnings. w3c/presentation-api#182.
-
Rename PresentationSession.join() to reconnect(). w3c/presentation-api#181.
-
Editorial changes to interoperability document. w3c/presentation-api#183.
-
-
10 pull requests received 40 new comments.
-
Add PresentationReceiver and navigator.presentation.receiver to access it. w3c/presentation-api#186 (21 comments by @anssiko, @markafoltz, @mounirlamouri, @tidoust)
-
Rename "presenting browsing context" to "receiving browsing context". w3c/presentation-api#191 (8 comments by @markafoltz, @mounirlamouri)
-
Make session a required argument when constructing a PresentationSessionConnect. w3c/presentation-api#185 (2 comments by @markafoltz, @mounirlamouri)
-
Rename "presenting browsing context" to "receiving browsing context" on "uc-req.md" file. w3c/presentation-api#196 (1 comment by @anssiko)
-
Reorder start steps to create session only when needed w3c/presentation-api#192 (1 comment by @markafoltz)
-
Rename PresentationSession.join() to reconnect(). w3c/presentation-api#181 (1 comment by @mounirlamouri)
-
Initial version of the interoperability document w3c/presentation-api#175 (1 comment by @louaybassbouss)
-
TR publications
-
1 document published.
-
Presentation API published as a Working Draft. History of Presentation API
-
GitHub
w3c/presentation-api
-
8 issues opened.
-
Rename PresentationSession to PresentationController w3c/presentation-api#171, by @avayvod.
-
Rename join() to something that reflects its intended use better w3c/presentation-api#170, by @avayvod.
-
conflict description for uniquely identifying a presentation session w3c/presentation-api#165, by @schien.
-
1-UA and 2-UA details w3c/presentation-api#164, by @hsablonniere.
-
PresentationSession should have stream interfaces! w3c/presentation-api#163, by @domenic.
-
Evaluate Presentation API against the Media Accessibility User Requirements spec w3c/presentation-api#162, by @tidoust.
-
Let getAvailability() resolve its promise as soon as availability has been tested w3c/presentation-api#161, by @foolip.
-
Availability URLs versus Presentation URLs w3c/presentation-api#154, by @markafoltz.
-
-
10 issues closed.
-
Let getAvailability() resolve its promise as soon as availability has been tested w3c/presentation-api#161.
-
1-UA and 2-UA details w3c/presentation-api#164.
-
Fullscreen vs Presentation API w3c/presentation-api#150.
-
Allow page to designate a default presentation URL w3c/presentation-api#26.
-
Review the use cases and requirements w3c/presentation-api#68.
-
Define return value for cancelled/missing session for startSession/joinSession w3c/presentation-api#20.
-
Specify behavior when multiple controlling pages are connected to the session w3c/presentation-api#19.
-
Is user permission required to prompt for screen availability information? w3c/presentation-api#10.
-
How to filter available screens according to the content being presented w3c/presentation-api#9.
-
Multiple presentation devices w3c/presentation-api#97.
-
-
1 issue reopened.
-
Let getAvailability() resolve its promise as soon as availability has been tested w3c/presentation-api#161, by @mounirlamouri.
-
-
19 issues received 60 new comments.
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153 (10 comments by @annevk, @anssiko, @hsablonniere, @louaybassbouss, @markafoltz, @tidoust)
-
1-UA and 2-UA details w3c/presentation-api#164 (10 comments by @anssiko, @avayvod, @hsablonniere, @tidoust)
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35 (8 comments by @avayvod, @markafoltz, @schien, @sicking)
-
Let getAvailability() resolve its promise as soon as availability has been tested w3c/presentation-api#161 (6 comments by @foolip, @markafoltz, @mounirlamouri)
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99 (5 comments by @hsablonniere, @markafoltz, @mounirlamouri)
-
PresentationSession should have stream interfaces! w3c/presentation-api#163 (4 comments by @avayvod, @domenic, @markafoltz)
-
Rename PresentationSession to PresentationController w3c/presentation-api#171 (3 comments by @avayvod, @markafoltz, @mounirlamouri)
-
Rename join() to something that reflects its intended use better w3c/presentation-api#170 (2 comments by @markafoltz, @schien)
-
Separate interface for controlling page and presenting page w3c/presentation-api#91 (1 comment by @mounirlamouri)
-
Allow page to designate a default presentation URL w3c/presentation-api#26 (1 comment by @mounirlamouri)
-
w3c/presentation-api#20 (1 comment by @mounirlamouri)
-
w3c/presentation-api#19 (1 comment by @mounirlamouri)
-
w3c/presentation-api#10 (1 comment by @mounirlamouri)
-
w3c/presentation-api#9 (1 comment by @mounirlamouri)
-
Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#86 (1 comment by @markafoltz)
-
-
21 pull requests opened.
-
Editorial: fix the the spec warnings. w3c/presentation-api#182, by @mounirlamouri.
-
Rename PresentationSession.join() to reconnect(). w3c/presentation-api#181, by @mounirlamouri.
-
(cleanup) set of availability objects: remove P from the tuple. w3c/presentation-api#180, by @mounirlamouri.
-
Resolve getAvailability with current status. w3c/presentation-api#179, by @mounirlamouri.
-
[publication] Updated URL passed to Echidna to use right Git branch w3c/presentation-api#178, by @tidoust.
-
Added ReSpec postprocessing to remove "for" attributes w3c/presentation-api#177, by @tidoust.
-
Initial version of the interoperability document w3c/presentation-api#175, by @louaybassbouss.
-
Hide issue summaries pulled from GH w3c/presentation-api#174, by @anssiko.
-
getAvailability: resolve with false if UA can't even start a session. w3c/presentation-api#173, by @mounirlamouri.
-
getAvailability() should return true if the list of displays isn't empty. w3c/presentation-api#172, by @mounirlamouri.
-
Use TIDY instead of TIDY-HTML5 to make it settable in from ENV. w3c/presentation-api#169, by @mounirlamouri.
-
Set tidy "preserve-entitites" config flag to preserve & escaping w3c/presentation-api#168, by @tidoust.
-
Add missing parenthesis in example 1 code w3c/presentation-api#167, by @hsablonniere.
-
Mention 1-UA and 2-UA cases explicitly in the introduction w3c/presentation-api#166, by @hsablonniere.
-
Editorial fixes w3c/presentation-api#160, by @anssiko.
-
PresentationRequest.start() requires a user gesture. w3c/presentation-api#159, by @mounirlamouri.
-
Pull in issue tracker data using GitHub API w3c/presentation-api#158, by @anssiko.
-
Use syntax highlighting in the examples w3c/presentation-api#157, by @anssiko.
-
Use「Living Document」convention for auto-publishing w3c/presentation-api#156, by @sideshowbarker.
-
Make changes suggested by @sicking w3c/presentation-api#155, by @markafoltz.
-
-
18 pull requests merged.
-
(cleanup) set of availability objects: remove P from the tuple. w3c/presentation-api#180.
-
Resolve getAvailability with current status. w3c/presentation-api#179.
-
getAvailability: resolve with false if UA can't even start a session. w3c/presentation-api#173.
-
Initial version of the interoperability document w3c/presentation-api#175.
-
[publication] Updated URL passed to Echidna to use right Git branch w3c/presentation-api#178.
-
Added ReSpec postprocessing to remove "for" attributes w3c/presentation-api#177.
-
Hide issue summaries pulled from GH w3c/presentation-api#174.
-
Editorial w3c/presentation-api#176.
-
getAvailability() should return true if the list of displays isn't empty. w3c/presentation-api#172.
-
Mention 1-UA and 2-UA cases explicitly in the introduction w3c/presentation-api#166.
-
Set tidy "preserve-entitites" config flag to preserve & escaping w3c/presentation-api#168.
-
Use TIDY instead of TIDY-HTML5 to make it settable in from ENV. w3c/presentation-api#169.
-
Add missing parenthesis in example 1 code w3c/presentation-api#167.
-
Editorial fixes w3c/presentation-api#160.
-
Pull in issue tracker data using GitHub API w3c/presentation-api#158.
-
PresentationRequest.start() requires a user gesture. w3c/presentation-api#159.
-
Use syntax highlighting in the examples w3c/presentation-api#157.
-
Make changes suggested by @sicking w3c/presentation-api#155.
-
-
2 pull requests closed.
-
Use「Living Document」convention for auto-publishing w3c/presentation-api#156.
-
default-presentation link type and browser initiated presentation algorithm w3c/presentation-api#87.
-
-
18 pull requests received 59 new comments.
-
Pull in issue tracker data using GitHub API w3c/presentation-api#158 (14 comments by @anssiko, @markafoltz, @mounirlamouri)
-
Initial version of the interoperability document w3c/presentation-api#175 (9 comments by @anssiko, @markafoltz)
-
getAvailability: resolve with false if UA can't even start a session. w3c/presentation-api#173 (8 comments by @markafoltz, @mounirlamouri)
-
Use TIDY instead of TIDY-HTML5 to make it settable in from ENV. w3c/presentation-api#169 (4 comments by @anssiko, @markafoltz, @mounirlamouri, @tidoust)
-
Add missing parenthesis in example 1 code w3c/presentation-api#167 (3 comments by @hsablonniere, @markafoltz, @mounirlamouri)
-
PresentationRequest.start() requires a user gesture. w3c/presentation-api#159 (3 comments by @anssiko, @avayvod, @mounirlamouri)
-
Rename PresentationSession.join() to reconnect(). w3c/presentation-api#181 (2 comments by @markafoltz)
-
getAvailability() should return true if the list of displays isn't empty. w3c/presentation-api#172 (2 comments by @avayvod, @markafoltz)
-
Mention 1-UA and 2-UA cases explicitly in the introduction w3c/presentation-api#166 (2 comments by @anssiko, @markafoltz)
-
Use「Living Document」convention for auto-publishing w3c/presentation-api#156 (2 comments by @anssiko, @sideshowbarker)
-
default-presentation link type and browser initiated presentation algorithm w3c/presentation-api#87 (2 comments by @markafoltz, @mounirlamouri)
-
(cleanup) set of availability objects: remove P from the tuple. w3c/presentation-api#180 (1 comment by @markafoltz)
-
Spec pubrules and Echidna compliant, WD generation semi-automated w3c/presentation-api#113 (1 comment by @tripu)
-
TR publications
-
1 document published.
-
Presentation API published as a Working Draft. History of Presentation API
-
Participants
-
1 organization left.
-
MStar Semiconductor, Inc. left.
-
GitHub
w3c/presentation-api
-
12 issues opened.
-
Assess interoperability of Presentation API implementations w3c/presentation-api#153, by @markafoltz.
-
Reconcile sessionavailable vs. sessionconnect for notifying page of session connection w3c/presentation-api#152, by @markafoltz.
-
Fullscreen vs Presentation API w3c/presentation-api#150, by @annevk.
-
Define behavior when sending a message to a PresentationSession fails w3c/presentation-api#149, by @markafoltz.
-
Run startSession steps in parallel w3c/presentation-api#148, by @obeletski.
-
Update PresentationAvailability.value and fire the change event in the same task w3c/presentation-api#143, by @foolip.
-
Missing "attribute" in "readonly DOMString? id;" w3c/presentation-api#142, by @foolip.
-
Replace PresentationSession[] with sequence<PresentationSession> w3c/presentation-api#141, by @foolip.
-
Section DefaultSessionStart should be DefaultSessionStartEvent w3c/presentation-api#140, by @foolip.
-
Use [SameObject] for Navigator.presentation w3c/presentation-api#139, by @foolip.
-
Remove getAvailability() url argument unless implemented w3c/presentation-api#138, by @foolip.
-
Rename NavigatorPresentation to just Presentation w3c/presentation-api#137, by @foolip.
-
-
10 issues closed.
-
Remove getAvailability() url argument unless implemented w3c/presentation-api#138.
-
Spec authoring tool migration w3c/presentation-api#116.
-
Update PresentationAvailability.value and fire the change event in the same task w3c/presentation-api#143.
-
Missing "attribute" in "readonly DOMString? id;" w3c/presentation-api#142.
-
Replace PresentationSession[] with sequence<PresentationSession> w3c/presentation-api#141.
-
Section DefaultSessionStart should be DefaultSessionStartEvent w3c/presentation-api#140.
-
Use [SameObject] for Navigator.presentation w3c/presentation-api#139.
-
Rename NavigatorPresentation to just Presentation w3c/presentation-api#137.
-
Section " Messaging between presentation sessions" should be updated w3c/presentation-api#121.
-
[meta] Working Draft publication requirements w3c/presentation-api#123.
-
-
12 issues received 41 new comments.
-
Remove getAvailability() url argument unless implemented w3c/presentation-api#138 (12 comments by @avayvod, @foolip, @markafoltz, @mwatson2)
-
Define behavior when sending a message to a PresentationSession fails w3c/presentation-api#149 (6 comments by @markafoltz, @mounirlamouri, @obeletski, @schien)
-
Allow page to designate a default presentation URL w3c/presentation-api#26 (6 comments by @avayvod, @tidoust)
-
Fullscreen vs Presentation API w3c/presentation-api#150 (3 comments by @annevk, @duanyao, @markafoltz)
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67 (3 comments by @louaybassbouss, @tidoust)
-
Update PresentationAvailability.value and fire the change event in the same task w3c/presentation-api#143 (1 comment by @markafoltz)
-
-
9 pull requests opened.
-
Editorial changes to pull request #146 w3c/presentation-api#151, by @markafoltz.
-
Fetch respec over HTTPS w3c/presentation-api#147, by @foolip.
-
Introduce PresentationRequest and defaultRequest. w3c/presentation-api#146, by @mounirlamouri.
-
Switched to ReSpec editing tool w3c/presentation-api#145, by @tidoust.
-
Addresses issues raised by @foolip w3c/presentation-api#144, by @markafoltz.
-
Obeletski messaging between sessions issue 121 w3c/presentation-api#136, by @markafoltz.
-
Obeletski new usecase issue 68 w3c/presentation-api#135, by @markafoltz.
-
Specify the DOMException name when rejecting a getAvailability() call. w3c/presentation-api#134, by @mounirlamouri.
-
Rename Availability interface to PresentationAvailability. w3c/presentation-api#133, by @mounirlamouri.
-
-
11 pull requests merged.
-
Editorial changes to pull request #146 w3c/presentation-api#151.
-
Introduce PresentationRequest and defaultRequest. w3c/presentation-api#146.
-
Fetch respec over HTTPS w3c/presentation-api#147.
-
Switched to ReSpec editing tool w3c/presentation-api#145.
-
Addresses issues raised by @foolip w3c/presentation-api#144.
-
Update to messaging section w3c/presentation-api#129.
-
Obeletski messaging between sessions issue 121 w3c/presentation-api#136.
-
Obeletski new usecase issue 68 w3c/presentation-api#135.
-
Added Pictionary use case w3c/presentation-api#131.
-
Specify the DOMException name when rejecting a getAvailability() call. w3c/presentation-api#134.
-
Rename Availability interface to PresentationAvailability. w3c/presentation-api#133.
-
-
8 pull requests received 39 new comments.
-
Introduce PresentationRequest and defaultRequest. w3c/presentation-api#146 (19 comments by @avayvod, @markafoltz, @mounirlamouri, @mwatson2)
-
Rename Availability interface to PresentationAvailability. w3c/presentation-api#133 (2 comments by @avayvod, @tidoust)
-
Specify the DOMException name when rejecting a getAvailability() call. w3c/presentation-api#134 (1 comment by @markafoltz)
-
GitHub
w3c/presentation-api
-
6 issues opened.
-
[meta] Working Draft publication requirements w3c/presentation-api#123, by @anssiko.
-
Section " Messaging between presentation sessions" should be updated w3c/presentation-api#121, by @obeletski.
-
Spec authoring tool migration w3c/presentation-api#116, by @anssiko.
-
Update the Status section, note stability per section w3c/presentation-api#112, by @anssiko.
-
Fix bugs related to PresentationSession.url attribute w3c/presentation-api#102, by @obeletski.
-
Define behavior of Window and Fullscreen APIs in the presentation browsing context w3c/presentation-api#99, by @markafoltz.
-
-
14 issues closed.
-
Necessity of an additional state to indicate a session was resumed w3c/presentation-api#12.
-
Timing of availablechange event to signal screen availability w3c/presentation-api#8.
-
Specify the NavigatorPresentation.session attribute and its related algorithms w3c/presentation-api#52.
-
Specify the presentation initialization algorithm w3c/presentation-api#34.
-
Make the Example section more concise w3c/presentation-api#42.
-
Resumption of multiple sessions w3c/presentation-api#39.
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46.
-
"Queue a task to fire an event named statechange at s.onstatechange. " makes no sense w3c/presentation-api#94.
-
URL schemes supported in presentation API w3c/presentation-api#76.
-
Define (cross) origin relationship between controller and presentation w3c/presentation-api#63.
-
Rethinking availability monitoring w3c/presentation-api#81.
-
Make the "set of presentations" variable global w3c/presentation-api#65.
-
Fix bugs related to PresentationSession.url attribute w3c/presentation-api#102.
-
Define a Multiplayer Gaming Use Case w3c/presentation-api#27.
-
-
1 issue reopened.
-
Screen availability mechanism for multiple sessions w3c/presentation-api#40, by @anssiko.
-
-
28 issues received 83 new comments.
-
Review the use cases and requirements w3c/presentation-api#68 (10 comments by @anssiko, @hongkicha, @louaybassbouss, @markafoltz, @obeletski, @tidoust)
-
Fix bugs related to PresentationSession.url attribute w3c/presentation-api#102 (8 comments by @markafoltz, @obeletski, @schien, @tidoust)
-
Rethinking availability monitoring w3c/presentation-api#81 (7 comments by @anssiko, @avayvod, @markafoltz, @obeletski)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (6 comments by @anssiko, @avayvod, @tidoust)
-
Separate interface for controlling page and presenting page w3c/presentation-api#91 (4 comments by @anssiko, @avayvod, @markafoltz)
-
Specify the presentation initialization algorithm w3c/presentation-api#34 (4 comments by @anssiko, @obeletski)
-
[meta] Working Draft publication requirements w3c/presentation-api#123 (3 comments by @anssiko, @markafoltz, @tidoust)
-
"Queue a task to fire an event named statechange at s.onstatechange. " makes no sense w3c/presentation-api#94 (3 comments by @anssiko, @markafoltz)
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46 (2 comments by @markafoltz, @tidoust)
-
URL schemes supported in presentation API w3c/presentation-api#76 (2 comments by @anssiko, @markafoltz)
-
Make the "set of presentations" variable global w3c/presentation-api#65 (2 comments by @anssiko, @markafoltz)
-
Presentations from within nested browsing contexts w3c/presentation-api#79 (2 comments by @anssiko, @markafoltz)
-
w3c/presentation-api#8 (1 comment by @markafoltz)
-
w3c/presentation-api#18 (1 comment by @markafoltz)
-
Section " Messaging between presentation sessions" should be updated w3c/presentation-api#121 (1 comment by @markafoltz)
-
Specify the NavigatorPresentation.session attribute and its related algorithms w3c/presentation-api#52 (1 comment by @markafoltz)
-
Update the Status section, note stability per section w3c/presentation-api#112 (1 comment by @tidoust)
-
Define (cross) origin relationship between controller and presentation w3c/presentation-api#63 (1 comment by @markafoltz)
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67 (1 comment by @matt-hammond-001)
-
Provide session lifecycle management for presenting page w3c/presentation-api#92 (1 comment by @anssiko)
-
-
29 pull requests opened.
-
Switch to use rawgit.com to serve released WD w3c/presentation-api#132, by @markafoltz.
-
Added Pictionary use case w3c/presentation-api#131, by @obeletski.
-
Update to resuming requirement w3c/presentation-api#130, by @obeletski.
-
Update to messaging section w3c/presentation-api#129, by @obeletski.
-
Update href for power saving requirement w3c/presentation-api#128, by @markafoltz.
-
A few typos and links to term definitions fixed w3c/presentation-api#127, by @tidoust.
-
Issue #68: Use cases and Requirements document updated w3c/presentation-api#126, by @louaybassbouss.
-
Reference WebIDL for DOMException instead of DOM w3c/presentation-api#125, by @dontcallmedom.
-
Updated version of PR#119: Initial description of session creation and monitoring in presenting w3c/presentation-api#122, by @markafoltz.
-
Fix send algorithm w3c/presentation-api#120, by @markafoltz.
-
fix send algorithm w3c/presentation-api#119, by @jcdufourd.
-
Initial description of session creation and monitoring in presenting … w3c/presentation-api#118, by @obeletski.
-
Second version of Issue #9: How to filter available screens according to the content being presented w3c/presentation-api#117, by @markafoltz.
-
Issue #46: Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#115, by @markafoltz.
-
Issue 9: How to filter available screens according to the content being presented w3c/presentation-api#114, by @markafoltz.
-
Spec pubrules and Echidna compliant, WD generation semi-automated w3c/presentation-api#113, by @tidoust.
-
Stylesheet tweaks w3c/presentation-api#111, by @anssiko.
-
Use HTTPS where possible w3c/presentation-api#110, by @mathiasbynens.
-
Issue #39: Drop presentationId from startSession w3c/presentation-api#109, by @markafoltz.
-
Update cross references to align with whatwg/xrefs w3c/presentation-api#108, by @markafoltz.
-
Simplify algorithm prose for starting, joining, establishing connection; use common idioms w3c/presentation-api#107, by @anssiko.
-
Fixes #102: Fix bugs related to PresentationSession.url attribute w3c/presentation-api#106, by @markafoltz.
-
Set presentations issue 65 w3c/presentation-api#105, by @anssiko.
-
Issue #45: Security and Privacy Considerations w3c/presentation-api#104, by @markafoltz.
-
Removed references to PresentationSession.url attribute (issue #102). w3c/presentation-api#103, by @obeletski.
-
Fix bugs in availablechange event w3c/presentation-api#101, by @markafoltz.
-
Provide a better definition for the global set of presentations. w3c/presentation-api#100, by @markafoltz.
-
Issue 68 w3c/presentation-api#98, by @louaybassbouss.
-
-
28 pull requests merged.
-
Switch to use rawgit.com to serve released WD w3c/presentation-api#132.
-
Update to resuming requirement w3c/presentation-api#130.
-
A few typos and links to term definitions fixed w3c/presentation-api#127.
-
Update href for power saving requirement w3c/presentation-api#128.
-
Issue #68: Use cases and Requirements document updated w3c/presentation-api#126.
-
Initial description of session creation and monitoring in presenting … w3c/presentation-api#118.
-
Updated version of PR#119: Initial description of session creation and monitoring in presenting w3c/presentation-api#122.
-
Issue 9: How to filter available screens according to the content being presented w3c/presentation-api#114.
-
Second version of Issue #9: How to filter available screens according to the content being presented w3c/presentation-api#117.
-
fix send algorithm w3c/presentation-api#119.
-
Fix send algorithm w3c/presentation-api#120.
-
Issue #46: Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#115.
-
Spec pubrules and Echidna compliant, WD generation semi-automated w3c/presentation-api#113.
-
Stylesheet tweaks w3c/presentation-api#111.
-
Issue #39: Drop presentationId from startSession w3c/presentation-api#109.
-
Update cross references to align with whatwg/xrefs w3c/presentation-api#108.
-
Simplify algorithm prose for starting, joining, establishing connection; use common idioms w3c/presentation-api#107.
-
Rethinking availability monitoring w3c/presentation-api#89.
-
Removed references to PresentationSession.url attribute (issue #102). w3c/presentation-api#103.
-
Fixes #102: Fix bugs related to PresentationSession.url attribute w3c/presentation-api#106.
-
Provide a better definition for the global set of presentations. w3c/presentation-api#100.
-
Set presentations issue 65 w3c/presentation-api#105.
-
Issue #45: Security and Privacy Considerations w3c/presentation-api#104.
-
Fix bugs in availablechange event w3c/presentation-api#101.
-
Update requirements for multiple controllers and presentations w3c/presentation-api#95.
-
Issue 68 w3c/presentation-api#98.
-
Add NOTE clarifying presentation URL scheme support w3c/presentation-api#96.
-
-
2 pull requests closed.
-
Reference WebIDL for DOMException instead of DOM w3c/presentation-api#125.
-
Use HTTPS where possible w3c/presentation-api#110.
-
-
1 pull request reopened.
-
Use HTTPS where possible w3c/presentation-api#110, by @anssiko.
-
-
22 pull requests received 84 new comments.
-
Rethinking availability monitoring w3c/presentation-api#89 (30 comments by @avayvod, @markafoltz, @mounirlamouri)
-
Second version of Issue #9: How to filter available screens according to the content being presented w3c/presentation-api#117 (11 comments by @avayvod, @markafoltz)
-
Spec pubrules and Echidna compliant, WD generation semi-automated w3c/presentation-api#113 (5 comments by @markafoltz, @tidoust)
-
Simplify algorithm prose for starting, joining, establishing connection; use common idioms w3c/presentation-api#107 (5 comments by @anssiko, @markafoltz)
-
Updated version of PR#119: Initial description of session creation and monitoring in presenting w3c/presentation-api#122 (4 comments by @anssiko, @markafoltz, @obeletski)
-
Update references in Terminology; editorial changes in SoTD, Introduction, Examples, Common idioms; rewording Availability w3c/presentation-api#124 (3 comments by @anssiko, @markafoltz)
-
Issue #39: Drop presentationId from startSession w3c/presentation-api#109 (3 comments by @avayvod, @markafoltz)
-
Provide a better definition for the global set of presentations. w3c/presentation-api#100 (2 comments by @anssiko, @markafoltz)
-
Issue #45: Security and Privacy Considerations w3c/presentation-api#104 (2 comments by @markafoltz, @tidoust)
-
Update requirements for multiple controllers and presentations w3c/presentation-api#95 (2 comments by @anssiko, @schien)
-
Issue #68: Use cases and Requirements document updated w3c/presentation-api#126 (1 comment by @markafoltz)
-
Initial description of session creation and monitoring in presenting … w3c/presentation-api#118 (1 comment by @markafoltz)
-
Add NOTE clarifying presentation URL scheme support w3c/presentation-api#96 (1 comment by @markafoltz)
-
GitHub
w3c/presentation-api
-
6 issues opened.
-
Multiple presentation devices w3c/presentation-api#97, by @obeletski.
-
"Queue a task to fire an event named statechange at s.onstatechange. " makes no sense w3c/presentation-api#94, by @smaug----.
-
Conformance classes definition w3c/presentation-api#93, by @tidoust.
-
Provide session lifecycle management for presenting page w3c/presentation-api#92, by @schien.
-
Separate interface for controlling page and presenting page w3c/presentation-api#91, by @schien.
-
Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#86, by @markafoltz.
-
-
1 issue reopened.
-
Allow page to designate a default presentation URL w3c/presentation-api#26, by @anssiko.
-
-
24 issues received 90 new comments.
-
Rethinking availability monitoring w3c/presentation-api#81 (20 comments by @anssiko, @avayvod, @markafoltz, @matt-hammond-001, @mwatson2, @obeletski, @tidoust)
-
Review the use cases and requirements w3c/presentation-api#68 (9 comments by @anssiko, @avayvod, @louaybassbouss, @markafoltz, @schien)
-
Define (cross) origin relationship between controller and presentation w3c/presentation-api#63 (7 comments by @anssiko, @markafoltz, @schien, @tidoust)
-
Security and privacy considerations w3c/presentation-api#45 (7 comments by @anssiko, @markafoltz, @tidoust)
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67 (5 comments by @matt-hammond-001, @obeletski)
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46 (5 comments by @anssiko, @matt-hammond-001, @tidoust)
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35 (4 comments by @markafoltz, @matt-hammond-001, @schien, @tidoust)
-
Allow page to turn itself into a presentation session w3c/presentation-api#32 (3 comments by @tidoust)
-
URL schemes supported in presentation API w3c/presentation-api#76 (3 comments by @anssiko, @louaybassbouss, @markafoltz)
-
Allow page to designate a default presentation URL w3c/presentation-api#26 (3 comments by @anssiko, @markafoltz)
-
Define algorithm for browser initiated presentation using default presentation URL w3c/presentation-api#86 (3 comments by @markafoltz, @mwatson2)
-
Screen availability mechanism for multiple sessions w3c/presentation-api#40 (2 comments by @anssiko, @tidoust)
-
w3c/presentation-api#9 (1 comment by @tidoust)
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80 (1 comment by @tidoust)
-
w3c/presentation-api#20 (1 comment by @schien)
-
w3c/presentation-api#18 (1 comment by @schien)
-
w3c/presentation-api#8 (1 comment by @schien)
-
-
8 pull requests opened.
-
Add NOTE clarifying presentation URL scheme support w3c/presentation-api#96, by @markafoltz.
-
Update requirements for multiple controllers and presentations w3c/presentation-api#95, by @markafoltz.
-
Drop the 'presentation' concept, it is not used anywhere. w3c/presentation-api#90, by @anssiko.
-
Rethinking availability monitoring w3c/presentation-api#89, by @avayvod.
-
Fixed typos and removed the 'origin' extraction step from the send() algorithm w3c/presentation-api#88, by @avayvod.
-
default-presentation link type and browser initiated presentation algorithm w3c/presentation-api#87, by @avayvod.
-
Fixed the structure of <section> tags in the spec HTML w3c/presentation-api#85, by @avayvod.
-
'data' is an attribute of the event w3c/presentation-api#84, by @anssiko.
-
-
5 pull requests merged.
-
Fixed typos and removed the 'origin' extraction step from the send() algorithm w3c/presentation-api#88.
-
Drop the 'presentation' concept, it is not used anywhere. w3c/presentation-api#90.
-
Added defaultsessionstart and default-presentation <link> to the spec w3c/presentation-api#77.
-
Fixed the structure of <section> tags in the spec HTML w3c/presentation-api#85.
-
'data' is an attribute of the event w3c/presentation-api#84.
-
-
5 pull requests received 13 new comments.
-
Added defaultsessionstart and default-presentation <link> to the spec w3c/presentation-api#77 (5 comments by @anssiko, @avayvod, @markafoltz)
-
Fixed the structure of <section> tags in the spec HTML w3c/presentation-api#85 (4 comments by @avayvod, @markafoltz)
-
Add NOTE clarifying presentation URL scheme support w3c/presentation-api#96 (2 comments by @louaybassbouss, @tidoust)
-
Fixed typos and removed the 'origin' extraction step from the send() algorithm w3c/presentation-api#88 (1 comment by @markafoltz)
-
default-presentation link type and browser initiated presentation algorithm w3c/presentation-api#87 (1 comment by @avayvod)
-
Participants
-
2 organizations joined.
-
Orange joined.
-
Samsung Electronics Co., Ltd. joined.
-
GitHub
w3c/presentation-api
-
5 issues opened.
-
Rethinking availability monitoring w3c/presentation-api#81, by @anssiko.
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80, by @markafoltz.
-
Presentations from within nested browsing contexts w3c/presentation-api#79, by @anssiko.
-
Define exceptions to be thrown in startSession and joinSession rejection w3c/presentation-api#78, by @markafoltz.
-
URL schemes supported in presentation API w3c/presentation-api#76, by @louaybassbouss.
-
-
2 issues closed.
-
Define exceptions to be thrown in startSession and joinSession rejection w3c/presentation-api#78.
-
The difference between index.html & Overview.src.html w3c/presentation-api#69.
-
-
9 issues received 23 new comments.
-
Rethinking availability monitoring w3c/presentation-api#81 (5 comments by @anssiko, @markafoltz, @mwatson2, @obeletski)
-
Presentations from within nested browsing contexts w3c/presentation-api#79 (4 comments by @anssiko, @louaybassbouss, @markafoltz)
-
Define exceptions to be thrown in startSession and joinSession rejection w3c/presentation-api#78 (3 comments by @anssiko, @markafoltz)
-
Specify the presentation initialization algorithm w3c/presentation-api#34 (3 comments by @anssiko, @obeletski)
-
URL schemes supported in presentation API w3c/presentation-api#76 (2 comments by @louaybassbouss, @markafoltz)
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46 (2 comments by @anssiko, @markafoltz)
-
The difference between index.html & Overview.src.html w3c/presentation-api#69 (2 comments by @anssiko, @hongkicha)
-
Define security requirements for messaging channel between secure origins w3c/presentation-api#80 (1 comment by @anssiko)
-
Allow page to designate a default presentation URL w3c/presentation-api#26 (1 comment by @markafoltz)
-
-
9 pull requests opened.
-
Update Editors. w3c/presentation-api#83, by @anssiko.
-
Declare DOMException types for rejected Promises w3c/presentation-api#82, by @markafoltz.
-
Added defaultsessionstart and default-presentation <link> to the spec w3c/presentation-api#77, by @avayvod.
-
A link to WG's charter w3c/presentation-api#75, by @hongkicha.
-
Link to the Work Mode in README w3c/presentation-api#74, by @anssiko.
-
Grammatical correction w3c/presentation-api#73, by @hongkicha.
-
Renamed postMessage() to send() to align with WebRTC DataChannel w3c/presentation-api#72, by @avayvod.
-
Fix syntax error in examples w3c/presentation-api#71, by @louaybassbouss.
-
Make Mark Foltz the co-editor w3c/presentation-api#70, by @anssiko.
-
-
8 pull requests merged.
-
Update Editors. w3c/presentation-api#83.
-
Declare DOMException types for rejected Promises w3c/presentation-api#82.
-
Renamed postMessage() to send() to align with WebRTC DataChannel w3c/presentation-api#72.
-
Link to the Work Mode in README w3c/presentation-api#74.
-
Grammatical correction w3c/presentation-api#73.
-
Fix syntax error in examples w3c/presentation-api#71.
-
Make Mark Foltz the co-editor w3c/presentation-api#70.
-
Example code conventions, factor our endSession() from setSession() w3c/presentation-api#66.
-
-
2 pull requests closed.
-
A link to WG's charter w3c/presentation-api#75.
-
Fixed broken fragments in the specification w3c/presentation-api#58.
-
-
6 pull requests received 18 new comments.
-
A link to WG's charter w3c/presentation-api#75 (6 comments by @anssiko, @hongkicha, @markafoltz, @tidoust)
-
Added defaultsessionstart and default-presentation <link> to the spec w3c/presentation-api#77 (4 comments by @anssiko, @avayvod, @markafoltz)
-
Fixed broken fragments in the specification w3c/presentation-api#58 (3 comments by @anssiko, @drott)
-
Renamed postMessage() to send() to align with WebRTC DataChannel w3c/presentation-api#72 (2 comments by @anssiko, @markafoltz)
-
GitHub
w3c/presentation-api
-
5 issues opened.
-
The difference between index.html & Overview.src.html w3c/presentation-api#69, by @hongkicha.
-
Review the use cases and requirements w3c/presentation-api#68, by @anssiko.
-
Investigate possible compatibility with HbbTV w3c/presentation-api#67, by @anssiko.
-
Make the "set of presentations" variable global w3c/presentation-api#65, by @anssiko.
-
Define (cross) origin relationship between controller and presentation w3c/presentation-api#63, by @drott.
-
-
11 issues received 34 new comments.
-
Allow page to designate a default presentation URL w3c/presentation-api#26 (8 comments by @anssiko, @avayvod, @markafoltz)
-
The difference between index.html & Overview.src.html w3c/presentation-api#69 (4 comments by @hongkicha, @louaybassbouss)
-
Make the Example section more concise w3c/presentation-api#42 (4 comments by @anssiko, @louaybassbouss)
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46 (2 comments by @avayvod, @drott)
-
w3c/presentation-api#10 (1 comment by @jcdufourd)
-
-
3 pull requests opened.
-
Example code conventions, factor our endSession() from setSession() w3c/presentation-api#66, by @anssiko.
-
Make the Example section more concise (Issue #42) w3c/presentation-api#64, by @louaybassbouss.
-
First version of postMessage and onmessage algorithms w3c/presentation-api#62, by @drott.
-
-
2 pull requests merged.
-
Make the Example section more concise (Issue #42) w3c/presentation-api#64.
-
First version of postMessage and onmessage algorithms w3c/presentation-api#62.
-
-
3 pull requests received 10 new comments.
-
First version of postMessage and onmessage algorithms w3c/presentation-api#62 (5 comments by @drott, @markafoltz)
-
Make the Example section more concise (Issue #42) w3c/presentation-api#64 (4 comments by @anssiko, @drott, @louaybassbouss)
-
Example code conventions, factor our endSession() from setSession() w3c/presentation-api#66 (1 comment by @louaybassbouss)
-
TR publications
-
1 document published.
-
Presentation API published as a First Public Working Draft. History of Presentation API
-
Participants
-
2 organizations joined.
-
LG Electronics joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/presentation-api
-
5 issues opened.
-
Add facility for the opening page to add cloud paired screens as presentation targets w3c/presentation-api#61, by @markafoltz.
-
[meta] First Public Working Draft publication requirements w3c/presentation-api#56, by @anssiko.
-
Use the latest general W3C Document License w3c/presentation-api#55, by @anssiko.
-
Specify the NavigatorPresentation.session attribute and its related algorithms w3c/presentation-api#52, by @anssiko.
-
Update Status of This Document w3c/presentation-api#47, by @anssiko.
-
-
9 issues closed.
-
Use the latest general W3C Document License w3c/presentation-api#55.
-
[meta] First Public Working Draft publication requirements w3c/presentation-api#56.
-
Multi-display support w3c/presentation-api#1.
-
Adding an asynchronous getter (Promise) for screen availability status w3c/presentation-api#11.
-
Finalize specification for reconnecting to existing presentations w3c/presentation-api#15.
-
Specify data types and API for messaging channel w3c/presentation-api#16.
-
Specify 1:n communication between a PresentationSession and multiple connected PresentationSession w3c/presentation-api#36.
-
Define lifetime of the presented document; when can the user agent close the document w3c/presentation-api#33.
-
Update Status of This Document w3c/presentation-api#47.
-
-
17 issues received 35 new comments.
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46 (6 comments by @anssiko, @drott, @markafoltz, @schien)
-
Make the Example section more concise w3c/presentation-api#42 (6 comments by @anssiko, @louaybassbouss, @markafoltz)
-
Specify the presentation initialization algorithm w3c/presentation-api#34 (2 comments by @anssiko, @markafoltz)
-
Add facility for the opening page to add cloud paired screens as presentation targets w3c/presentation-api#61 (1 comment by @louaybassbouss)
-
[meta] First Public Working Draft publication requirements w3c/presentation-api#56 (1 comment by @tidoust)
-
w3c/presentation-api#8 (1 comment by @markafoltz)
-
w3c/presentation-api#15 (1 comment by @markafoltz)
-
w3c/presentation-api#16 (1 comment by @markafoltz)
-
Specify 1:n communication between a PresentationSession and multiple connected PresentationSession w3c/presentation-api#36 (1 comment by @markafoltz)
-
w3c/presentation-api#21 (1 comment by @markafoltz)
-
Refine how to do session teardown/disconnect/closing w3c/presentation-api#35 (1 comment by @markafoltz)
-
Define lifetime of the presented document; when can the user agent close the document w3c/presentation-api#33 (1 comment by @markafoltz)
-
-
10 pull requests opened.
-
Update the canonical link relation to help search engines find the latest w3c/presentation-api#60, by @anssiko.
-
Redirect FPWD in staging to published w3c/presentation-api#59, by @anssiko.
-
Fixed broken fragments in the specification w3c/presentation-api#58, by @tidoust.
-
Rolled back Copyright notice to the usual one w3c/presentation-api#57, by @tidoust.
-
Use the custom W3C Document License defined in the Charter w3c/presentation-api#54, by @anssiko.
-
Make the spec (more) Pubrules compliant; add FPWD snapshot w3c/presentation-api#53, by @anssiko.
-
Minor edits w3c/presentation-api#51, by @drott.
-
Cross reference GitHub issues in the specification w3c/presentation-api#50, by @markafoltz.
-
Added a custom paragraph in Status of This Document section (#47) w3c/presentation-api#49, by @tidoust.
-
Editorial: sort attributes alphabetically from A to Z. w3c/presentation-api#48, by @anssiko.
-
-
9 pull requests merged.
-
Update the canonical link relation to help search engines find the latest w3c/presentation-api#60.
-
Redirect FPWD in staging to published w3c/presentation-api#59.
-
Rolled back Copyright notice to the usual one w3c/presentation-api#57.
-
Use the custom W3C Document License defined in the Charter w3c/presentation-api#54.
-
Make the spec (more) Pubrules compliant; add FPWD snapshot w3c/presentation-api#53.
-
Minor edits w3c/presentation-api#51.
-
Cross reference GitHub issues in the specification w3c/presentation-api#50.
-
Added a custom paragraph in Status of This Document section (#47) w3c/presentation-api#49.
-
Editorial: sort attributes alphabetically from A to Z. w3c/presentation-api#48.
-
-
5 pull requests received 11 new comments.
-
Cross reference GitHub issues in the specification w3c/presentation-api#50 (4 comments by @anssiko, @drott)
-
Redirect FPWD in staging to published w3c/presentation-api#59 (2 comments by @anssiko, @marcoscaceres)
-
Make the spec (more) Pubrules compliant; add FPWD snapshot w3c/presentation-api#53 (2 comments by @drott)
-
Added a custom paragraph in Status of This Document section (#47) w3c/presentation-api#49 (1 comment by @anssiko)
-
Participants
-
1 organization joined.
-
British Broadcasting Corporation joined.
-
GitHub
w3c/presentation-api
-
5 issues opened.
-
Define a bi-directional data channel between opening and presenting browsing contexts w3c/presentation-api#46, by @drott.
-
Security and privacy considerations w3c/presentation-api#45, by @anssiko.
-
Make the Example section more concise w3c/presentation-api#42, by @anssiko.
-
Screen availability mechanism for multiple sessions w3c/presentation-api#40, by @tidoust.
-
Resumption of multiple sessions w3c/presentation-api#39, by @tidoust.
-
-
3 issues received 3 new comments.
-
Specify 1:n communication between a PresentationSession and multiple connected PresentationSession w3c/presentation-api#36 (1 comment by @anssiko)
-
4 pull requests opened.
-
Add CONTRIBUTING.md. w3c/presentation-api#44, by @anssiko.
-
Addressing Anssi's feedback, expanding the noted items w3c/presentation-api#43, by @drott.
-
Move prose below the corresponding IDL blocks; other editorial changes w3c/presentation-api#41, by @anssiko.
-
Updated Mark's PR w3c/presentation-api#38, by @drott.
-
-
4 pull requests merged.
-
Add CONTRIBUTING.md. w3c/presentation-api#44.
-
Move prose below the corresponding IDL blocks; other editorial changes w3c/presentation-api#41.
-
Addressing Anssi's feedback, expanding the noted items w3c/presentation-api#43.
-
Updated Mark's PR w3c/presentation-api#38.
-
-
1 pull request closed.
-
First draft of algorithms for the specification. w3c/presentation-api#37.
-
-
4 pull requests received 9 new comments.
-
Addressing Anssi's feedback, expanding the noted items w3c/presentation-api#43 (6 comments by @anssiko, @drott, @markafoltz)
-