Second Screen Working Group - Activity in 2022
No matches.
TR publications
-
3 documents published.
-
Multi-Screen Window Placement published twice as a Working Draft. History of Multi-Screen Window Placement
-
Open Screen Protocol published as a Working Draft. History of Open Screen Protocol
-
GitHub
w3c/presentation-api
-
2 issues opened.
-
Cannot find name 'PresentationRequest' w3c/presentation-api#510, by @abutizi.
-
Update spec language to refer to child navigables instead of nested browing contexts? w3c/presentation-api#509, by @markafoltz.
-
-
1 issue closed.
-
Cannot find name 'PresentationRequest' w3c/presentation-api#510.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
debug `EXAMPLE 6` w3c/presentation-api#513, by @youkinjoh.
-
typo say hello w3c/presentation-api#512, by @youkinjoh.
-
debug `EXAMPLE 7` w3c/presentation-api#511, by @youkinjoh.
-
typo remove method w3c/presentation-api#508, by @youkinjoh.
-
-
1 pull request merged.
-
typo remove method w3c/presentation-api#508.
-
-
4 pull requests received 6 new comments.
w3c/window-management
-
4 issues opened.
-
Move existing methods of inferring multi-montior support behind permission w3c/window-management#123, by @pes10k.
-
Security considerations section links to non-versioned GH doc w3c/window-management#122, by @pes10k.
-
Screen labels seem especially privacy risking and identifying w3c/window-management#121, by @pes10k.
-
isExtended is additional fingerprinting surface w3c/window-management#120, by @pes10k.
-
-
3 issues received 4 new comments.
-
2 pull requests opened.
-
Permission-policy w3c/window-management#124, by @michaelwasserman.
-
Add Explainer for permission Rename w3c/window-management#119, by @bradtriebwasser.
-
-
2 pull requests merged.
-
Permission-policy w3c/window-management#124.
-
Add Explainer for permission Rename w3c/window-management#119.
-
-
1 pull request received 9 new comments.
w3c/openscreenprotocol
-
1 pull request opened.
-
Fix broken references to API specs w3c/openscreenprotocol#307, by @tidoust.
-
-
1 pull request merged.
-
Fix broken references to API specs w3c/openscreenprotocol#307.
-
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Open Screen Protocol published twice as a Working Draft. History of Open Screen Protocol
-
Multi-Screen Window Placement published as a Working Draft. History of Multi-Screen Window Placement
-
GitHub
w3c/window-management
-
2 issues opened.
-
Internationalization Checklist w3c/window-management#118, by @anssiko.
-
Accessibility Checklist w3c/window-management#117, by @anssiko.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Drop broken link to now gone "window-placement" permission w3c/window-management#116, by @tidoust.
-
-
1 pull request merged.
-
Drop broken link to now gone "window-placement" permission w3c/window-management#116.
-
-
1 pull request received 1 new comment.
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107 (1 comment by @tidoust)
-
w3c/openscreenprotocol
-
1 issue opened.
-
MIME types and metadata encoding for Dolby Vision formats w3c/openscreenprotocol#306, by @markafoltz.
-
-
4 issues closed.
-
Clarify the supported signature algorithms for certificates w3c/openscreenprotocol#280.
-
The keyUsage name is digitalSignature, not signing w3c/openscreenprotocol#279.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194.
-
Cross-spec links are broken w3c/openscreenprotocol#303.
-
-
4 issues received 4 new comments.
-
Clarify the supported signature algorithms for certificates w3c/openscreenprotocol#280 (1 comment by @markafoltz)
-
The keyUsage name is digitalSignature, not signing w3c/openscreenprotocol#279 (1 comment by @markafoltz)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (1 comment by @markafoltz)
-
-
2 pull requests merged.
-
Fixes algorithm and signing fields in agent certificate. w3c/openscreenprotocol#288.
-
Add transfer-functions and hdr-metadata to video-capabilities. w3c/openscreenprotocol#300.
-
-
2 pull requests received 5 new comments.
-
Fixes algorithm and signing fields in agent certificate. w3c/openscreenprotocol#288 (3 comments by @markafoltz)
-
Add transfer-functions and hdr-metadata to video-capabilities. w3c/openscreenprotocol#300 (2 comments by @markafoltz)
-
TR publications
-
1 document published.
-
Open Screen Protocol published as a Working Draft. History of Open Screen Protocol
-
GitHub
w3c/window-management
-
1 issue opened.
-
Change "window-placement" permission and spec name to "window-management" w3c/window-management#114, by @bradtriebwasser.
-
-
2 issues received 3 new comments.
-
window.open should support the 'fullscreen' option w3c/window-management#7 (2 comments by @bradtriebwasser, @NielsLeenheer)
-
Change "window-placement" permission and spec name to "window-management" w3c/window-management#114 (1 comment by @bradtriebwasser)
-
-
1 pull request opened.
-
Replace `window-placement` permission references with `window-management` w3c/window-management#115, by @bradtriebwasser.
-
-
1 pull request merged.
-
Replace `window-placement` permission references with `window-management` w3c/window-management#115.
-
-
2 pull requests received 10 new comments.
-
Replace `window-placement` permission references with `window-management` w3c/window-management#115 (7 comments by @bradtriebwasser, @michaelwasserman)
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107 (3 comments by @bradtriebwasser)
-
w3c/openscreenprotocol
-
2 issues opened.
-
`color-gamuts` could be a single value and not a list w3c/openscreenprotocol#305, by @markafoltz.
-
How to control the sender side on the receiver side w3c/openscreenprotocol#304, by @segeter.
-
-
1 issue closed.
-
How to control the sender side on the receiver side w3c/openscreenprotocol#304.
-
-
1 issue received 5 new comments.
-
1 pull request merged.
-
Attempt to fix the spec. w3c/openscreenprotocol#302.
-
-
1 pull request received 7 new comments.
-
Add transfer-functions and hdr-metadata to video-capabilities. w3c/openscreenprotocol#300 (7 comments by @chrisn, @markafoltz)
-
TR publications
-
6 documents published.
-
Remote Playback API published twice as a Candidate Recommendation Draft. History of Remote Playback API
-
Multi-Screen Window Placement published as a Working Draft. History of Multi-Screen Window Placement
-
Open Screen Protocol published 3 times as a Working Draft. History of Open Screen Protocol
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Rang-Hyuck Lee (Gooroomee Inc.) joined.
-
Geunhyung Kim (Gooroomee Inc.) joined.
-
Fangzhen Song (ByteDance) joined.
-
-
1 organization joined.
-
Gooroomee Inc. joined.
-
GitHub
w3c/openscreenprotocol
-
1 issue opened.
-
Cross-spec links are broken w3c/openscreenprotocol#303, by @markafoltz.
-
-
5 issues closed.
-
Use the same codec names as the media APIs. w3c/openscreenprotocol#233.
-
Consider removing support for P-521 w3c/openscreenprotocol#277.
-
Clarify `time-scale` field w3c/openscreenprotocol#287.
-
Set up tavis-cl process to regenerate HTML files. w3c/openscreenprotocol#199.
-
travis-ci jobs to commit index.html changes are failing w3c/openscreenprotocol#259.
-
-
9 issues received 11 new comments.
-
Adjust cipher and signature algorithm preference list for hardware w3c/openscreenprotocol#218 (2 comments by @markafoltz)
-
Do not use Distinguished Name to convey protocol details w3c/openscreenprotocol#278 (1 comment by @markafoltz)
-
Certificates should have a maximum lifetime, and SPAKE2 identities should be SPKI not cert fingerprint w3c/openscreenprotocol#282 (1 comment by @markafoltz)
-
Set up tavis-cl process to regenerate HTML files. w3c/openscreenprotocol#199 (1 comment by @markafoltz)
-
travis-ci jobs to commit index.html changes are failing w3c/openscreenprotocol#259 (1 comment by @markafoltz)
-
[Privacy] Fate of metadata / authentication history when clearing browsing data w3c/openscreenprotocol#132 (1 comment by @markafoltz)
-
-
11 pull requests opened.
-
Attempt to fix the spec. w3c/openscreenprotocol#302, by @markafoltz.
-
Define the agent fingerprint as the SPKI. w3c/openscreenprotocol#301, by @markafoltz.
-
Add transfer-functions and hdr-metadata to video-capabilities. w3c/openscreenprotocol#300, by @markafoltz.
-
Reference WebCodecs registry for codec names. w3c/openscreenprotocol#299, by @markafoltz.
-
Explain what a time scale is. w3c/openscreenprotocol#298, by @markafoltz.
-
Simplify TLS requirements so we don't have to recommend algorithms. w3c/openscreenprotocol#297, by @markafoltz.
-
Adds appendix with PSK specifications. w3c/openscreenprotocol#296, by @markafoltz.
-
Remove P-521 curve from agent certificate requirements w3c/openscreenprotocol#295, by @markafoltz.
-
Update for SPAKE2 w3c/openscreenprotocol#294, by @markafoltz.
-
Add an algorithm for setting the agent certificate serial number w3c/openscreenprotocol#293, by @markafoltz.
-
Update pygmentize_dir.py for Pygments 2.13.0 w3c/openscreenprotocol#292, by @markafoltz.
-
-
4 pull requests merged.
-
Reference WebCodecs registry for codec names. w3c/openscreenprotocol#299.
-
Remove P-521 curve from agent certificate requirements w3c/openscreenprotocol#295.
-
Explain what a time scale is. w3c/openscreenprotocol#298.
-
Update pygmentize_dir.py for Pygments 2.13.0 w3c/openscreenprotocol#292.
-
-
8 pull requests received 22 new comments.
-
Fixes algorithm and signing fields in agent certificate. w3c/openscreenprotocol#288 (10 comments by @chrisn, @markafoltz, @tidoust)
-
Add transfer-functions and hdr-metadata to video-capabilities. w3c/openscreenprotocol#300 (2 comments by @markafoltz)
-
Remove P-521 curve from agent certificate requirements w3c/openscreenprotocol#295 (1 comment by @markafoltz)
-
Add an algorithm for setting the agent certificate serial number w3c/openscreenprotocol#293 (1 comment by @markafoltz)
-
w3c/window-management
-
3 issues opened.
-
Wide review tracker w3c/window-management#110, by @ghurlbot.
-
setup automated publication for Multi-Screen Window Placement API working drafts w3c/window-management#111, by @ghurlbot.
-
1 issue closed.
-
setup automated publication for Multi-Screen Window Placement API working drafts w3c/window-management#111.
-
-
3 issues received 8 new comments.
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98 (5 comments by @michaelwasserman, @morsssss, @nadavsinai-philips, @tarasinf)
-
Provide Physical Dimensions / PPI of Displays w3c/window-management#65 (2 comments by @nicksherman, @patrickhlauke)
-
setup automated publication for Multi-Screen Window Placement API working drafts w3c/window-management#111 (1 comment by @inexorabletash)
-
-
1 pull request opened.
-
Enable auto-publication to /TR w3c/window-management#112, by @tidoust.
-
-
2 pull requests merged.
-
Enable auto-publication to /TR w3c/window-management#112.
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107.
-
-
2 pull requests received 11 new comments.
-
Enable auto-publication to /TR w3c/window-management#112 (6 comments by @michaelwasserman, @tidoust)
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107 (5 comments by @inexorabletash, @michaelwasserman, @tidoust)
-
w3c/presentation-api
-
1 issue opened.
-
PresentationRequest.getAvailability() could always return a new Promise w3c/presentation-api#507, by @markafoltz.
-
w3c/remote-playback
-
2 issues received 2 new comments.
-
Remote Playback API tests and implementation report w3c/remote-playback#92 (1 comment by @FritzHeiden)
-
2 pull requests opened.
-
Fix ReSpec definitions of RemotePlayback interface and other issues. w3c/remote-playback#151, by @markafoltz.
-
Move Mounir to former editors w3c/remote-playback#148, by @johannhof.
-
-
2 pull requests merged.
-
Fix ReSpec definitions of RemotePlayback interface and other issues. w3c/remote-playback#151.
-
Move Mounir to former editors w3c/remote-playback#148.
-
-
2 pull requests received 13 new comments.
-
Fix ReSpec definitions of RemotePlayback interface and other issues. w3c/remote-playback#151 (12 comments by @markafoltz, @tidoust)
-
w3c/secondscreen-wg
-
1 issue received 1 new comment.
GitHub
w3c/window-management
-
1 issue opened.
-
ScreenDetailed height, availHeight, width, and availWidth w3c/window-management#109, by @digisparkflow.
-
-
1 issue closed.
-
ScreenDetailed height, availHeight, width, and availWidth w3c/window-management#109.
-
-
5 issues received 12 new comments.
-
Exposing the refresh rate of displays w3c/window-management#47 (4 comments by @jespertheend, @michaelwasserman)
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98 (3 comments by @fortheday001, @morsssss)
-
ScreenDetailed height, availHeight, width, and availWidth w3c/window-management#109 (2 comments by @inexorabletash)
-
window.open should support the 'fullscreen' option w3c/window-management#7 (1 comment by @michaelwasserman)
-
Participants
-
1 participant left.
-
Mounir Lamouri (Google LLC) left.
-
GitHub
w3c/window-management
-
1 issue received 1 new comment.
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98 (1 comment by @fortheday001)
-
-
1 pull request opened.
-
Clarify that screen labels are for users only. w3c/window-management#108, by @bradtriebwasser.
-
-
1 pull request merged.
-
Clarify that screen labels are for users only. w3c/window-management#108.
-
-
1 pull request received 2 new comments.
-
Clarify that screen labels are for users only. w3c/window-management#108 (2 comments by @bradtriebwasser, @michaelwasserman)
-
TR publications
-
3 documents published.
-
Remote Playback API published as a Candidate Recommendation Draft. History of Remote Playback API
-
Presentation API published as a Candidate Recommendation Draft. History of Presentation API
-
Multi-Screen Window Placement published as a First Public Working Draft. History of Multi-Screen Window Placement
-
Past meetings
GitHub
w3c/window-management
-
2 issues opened.
-
This API cannot be used in the http environment, is there a solution? w3c/window-management#106, by @342x.
-
[Question] Typescript Support w3c/window-management#103, by @argmichael.
-
-
2 issues closed.
-
This API cannot be used in the http environment, is there a solution? w3c/window-management#106.
-
[Question] Typescript Support w3c/window-management#103.
-
-
3 issues received 6 new comments.
-
This API cannot be used in the http environment, is there a solution? w3c/window-management#106 (2 comments by @anssiko, @Garbee)
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98 (2 comments by @lcl45, @morsssss)
-
-
4 pull requests opened.
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107, by @tidoust.
-
Use DOM-recommended phrasing for 'fire an event' w3c/window-management#105, by @dontcallmedom.
-
Minor editorial fixes to prepare FPWD w3c/window-management#104, by @tidoust.
-
Add note about empty string in screen labels. w3c/window-management#102, by @bradtriebwasser.
-
-
4 pull requests merged.
-
Minor editorial fixes to prepare FPWD w3c/window-management#104.
-
Use DOM-recommended phrasing for 'fire an event' w3c/window-management#105.
-
Add an outline for initiating multi-screen experiences w3c/window-management#101.
-
Add note about empty string in screen labels. w3c/window-management#102.
-
-
4 pull requests received 26 new comments.
-
Add note about empty string in screen labels. w3c/window-management#102 (10 comments by @anssiko, @bradtriebwasser, @michaelwasserman, @w3cbot)
-
Minor editorial fixes to prepare FPWD w3c/window-management#104 (7 comments by @anssiko, @inexorabletash, @michaelwasserman, @tidoust)
-
Fix shortname, update permanent redirects, improve xref w3c/window-management#107 (5 comments by @anssiko, @inexorabletash, @michaelwasserman, @tidoust)
-
Add an outline for initiating multi-screen experiences w3c/window-management#101 (4 comments by @michaelwasserman, @reillyeon)
-
w3c/secondscreen-wg
-
1 issue opened.
-
Second Screen WG/CG - TPAC 2022 agenda w3c/secondscreen-wg#6, by @anssiko.
-
-
1 issue received 4 new comments.
-
Second Screen WG/CG - 2022 Q2 virtual meeting w3c/secondscreen-wg#4 (4 comments by @anssiko, @chrisn, @markafoltz, @michaelwasserman)
-
w3c/openscreenprotocol
-
2 issues received 6 new comments.
-
Use the same codec names as the media APIs. w3c/openscreenprotocol#233 (4 comments by @chrisn, @markafoltz)
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (2 comments by @markafoltz)
-
w3c/presentation-api
-
3 issues opened.
-
Update spec language around 1-UA mode to reflect Multi-Screen Window Placement w3c/presentation-api#506, by @markafoltz.
-
Presentation of objects prototyping w3c/presentation-api#505, by @ghurlbot.
-
update status for issue #347 (Local Presentation API to enable child-window presentation documents) w3c/presentation-api#504, by @ghurlbot.
-
-
2 issues closed.
-
Presentation of objects prototyping w3c/presentation-api#505.
-
update status for issue #347 (Local Presentation API to enable child-window presentation documents) w3c/presentation-api#504.
-
-
5 issues received 7 new comments.
-
Local Presentation API to enable child-window presentation documents w3c/presentation-api#347 (2 comments by @anssiko, @markafoltz)
-
Update spec language around 1-UA mode to reflect Multi-Screen Window Placement w3c/presentation-api#506 (1 comment by @tidoust)
-
update status for issue #347 (Local Presentation API to enable child-window presentation documents) w3c/presentation-api#504 (1 comment by @anssiko)
-
1 pull request opened.
-
Update Use Cases and Requirements reference w3c/presentation-api#503, by @anssiko.
-
-
1 pull request merged.
-
Update Use Cases and Requirements reference w3c/presentation-api#503.
-
-
1 pull request received 1 new comment.
w3c/remote-playback
-
1 pull request opened.
-
Mark up definition of events as such w3c/remote-playback#147, by @dontcallmedom.
-
-
1 pull request merged.
-
Mark up definition of events as such w3c/remote-playback#147.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant joined.
-
Brad Triebwasser (Google LLC) joined.
-
-
4 participants left.
-
Tianqi Han (Shukun (Beijing) Network Technology Co., Ltd.) left.
-
Diego Gonzalez-Zuniga (Microsoft Corporation) left.
-
Daniel Libby (Microsoft Corporation) left.
-
Geunhyung Kim (Gooroomee Inc.) left.
-
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/window-management
-
1 issue opened.
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98, by @michaelwasserman.
-
-
3 issues received 4 new comments.
-
Support for programmatically set of the permission: add a specific command line argument? w3c/window-management#96 (2 comments by @matteotrapani, @reillyeon)
-
Feature Request: Initiate a multi-screen experience from a single user activation w3c/window-management#98 (1 comment by @michaelwasserman)
-
-
4 pull requests opened.
-
Add an outline for initiating multi-screen experiences w3c/window-management#101, by @michaelwasserman.
-
Clarify deceptive cross-screen placement security considerations w3c/window-management#100, by @michaelwasserman.
-
Editorial: Fix a couple typos w3c/window-management#99, by @miketaylr.
-
Move former editor Victor Costan to acknowledgements w3c/window-management#97, by @michaelwasserman.
-
-
3 pull requests merged.
-
Clarify deceptive cross-screen placement security considerations w3c/window-management#100.
-
Editorial: Fix a couple typos w3c/window-management#99.
-
Move former editor Victor Costan to acknowledgements w3c/window-management#97.
-
-
2 pull requests received 6 new comments.
-
Add an outline for initiating multi-screen experiences w3c/window-management#101 (3 comments by @michaelwasserman, @tomayac)
-
Move former editor Victor Costan to acknowledgements w3c/window-management#97 (3 comments by @anssiko, @michaelwasserman)
-
w3c/secondscreen-wg
-
1 issue received 2 new comments.
TR publications
-
3 documents published.
-
Presentation API published as a Candidate Recommendation Draft. History of Presentation API
-
Remote Playback API published as a Candidate Recommendation Draft. History of Remote Playback API
-
Open Screen Protocol published as a Working Draft. History of Open Screen Protocol
-
Participants
-
1 participant joined.
-
Alexis Menard (Intel Corporation) joined.
-
-
6 organizations joined.
-
The New York Times joined.
-
LG Electronics joined.
-
British Broadcasting Corporation joined.
-
ByteDance joined.
-
Fraunhofer Gesellschaft joined.
-
Google LLC joined.
-
GitHub
w3c/secondscreen-wg
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Multi-Screen Window Placement CG->WG w3c/secondscreen-wg#5, by @anssiko.
-
-
1 pull request merged.
-
Multi-Screen Window Placement CG->WG w3c/secondscreen-wg#5.
-
w3c/remote-playback
-
2 pull requests opened.
-
Enable auto-publication of the spec to /TR w3c/remote-playback#146, by @tidoust.
-
Fix markup for definition of watchAvailability() w3c/remote-playback#145, by @tidoust.
-
-
2 pull requests merged.
-
Enable auto-publication of the spec to /TR w3c/remote-playback#146.
-
Fix markup for definition of watchAvailability() w3c/remote-playback#145.
-
-
2 pull requests received 3 new comments.
-
Fix markup for definition of watchAvailability() w3c/remote-playback#145 (2 comments by @markafoltz, @tidoust)
-
w3c/presentation-api
-
2 pull requests opened.
-
Enable auto-publication of the spec to /TR w3c/presentation-api#502, by @tidoust.
-
Add the websockets spec to the list of xref sources w3c/presentation-api#501, by @tidoust.
-
-
2 pull requests merged.
-
Enable auto-publication of the spec to /TR w3c/presentation-api#502.
-
Add the websockets spec to the list of xref sources w3c/presentation-api#501.
-
-
2 pull requests received 3 new comments.
-
Add the websockets spec to the list of xref sources w3c/presentation-api#501 (2 comments by @markafoltz, @tidoust)
-
w3c/openscreenprotocol
-
1 pull request opened.
-
Enable auto-publication of WD to /TR w3c/openscreenprotocol#291, by @tidoust.
-
-
1 pull request merged.
-
Enable auto-publication of WD to /TR w3c/openscreenprotocol#291.
-
w3c/window-management
-
3 issues opened.
-
Support for programmatically set of the permission: add a specific command line argument? w3c/window-management#96, by @matteotrapani.
-
Are moveTo and resizeTo meant to be clamped to individual screens w3c/window-management#94, by @jpambrun.
-
Transfer GH repo to stage for First Public Working Draft w3c/window-management#93, by @anssiko.
-
-
3 issues closed.
-
Support for programmatically set of the permission: add a specific command line argument? w3c/window-management#96.
-
Transfer GH repo to stage for First Public Working Draft w3c/window-management#93.
-
Are moveTo and resizeTo meant to be clamped to individual screens w3c/window-management#94.
-
-
6 issues received 15 new comments.
-
Transfer GH repo to stage for First Public Working Draft w3c/window-management#93 (5 comments by @anssiko, @michaelwasserman, @tidoust)
-
Feature request: Fullscreen support on multiple screens w3c/window-management#92 (5 comments by @jpambrun, @michaelwasserman, @shizukanaqun)
-
allow window minimize & restore (focus) w3c/window-management#3 (2 comments by @ivansandrk, @jpambrun)
-
Support for programmatically set of the permission: add a specific command line argument? w3c/window-management#96 (1 comment by @reillyeon)
-
Are moveTo and resizeTo meant to be clamped to individual screens w3c/window-management#94 (1 comment by @michaelwasserman)
-
-
1 pull request opened.
-
Adjust boilerplate texts for migration to WG w3c/window-management#95, by @tidoust.
-
-
1 pull request merged.
-
Adjust boilerplate texts for migration to WG w3c/window-management#95.
-
Lifecycle
-
1 charter started.
-
Chartered until 31 January 2024. Participants had to rejoin under this charter.
-
Participants
-
1 participant joined.
-
Brian Zhang (Lenovo) joined.
-
-
1 participant left.
-
Brandon Tolsch (Google LLC) left.
-
-
2 organizations joined.
-
Lenovo joined.
-
Intel Corporation joined.
-
-
12 organizations left.
-
ByteDance left.
-
The New York Times left.
-
Shukun (Beijing) Network Technology Co., Ltd. left.
-
Lenovo left.
-
Gooroomee Inc. left.
-
LG Electronics left.
-
Google LLC left.
-
Intel Corporation left.
-
Fraunhofer Gesellschaft left.
-
Microsoft Corporation left.
-
Apple Inc. left.
-
British Broadcasting Corporation left.
-
GitHub
w3c/window-management
-
2 issues opened.
-
Feature request: Fullscreen support on multiple screens w3c/window-management#92, by @shizukanaqun.
-
Specify behavior for browsers that do not want to reveal screen plurality via `Screen.isExtended` w3c/window-management#91, by @michaelwasserman.
-
w3c/secondscreen-wg
-
1 issue opened.
-
Second Screen WG/CG - 2022 Q2 virtual meeting w3c/secondscreen-wg#4, by @anssiko.
-
w3c/secondscreen-charter
-
1 issue opened.
-
Consider aligning success criteria and working mode with Web Apps charter w3c/secondscreen-charter#37, by @tidoust.
-
GitHub
w3c/window-management
-
2 issues opened.
-
Is ScreenDetails supposed to inherit from EventTarget? w3c/window-management#90, by @RByers.
-
Add "window-placement" to Powerful Features Registry (rather than Permissions) w3c/window-management#89, by @miketaylr.
-
-
3 issues closed.
-
Is ScreenDetails supposed to inherit from EventTarget? w3c/window-management#90.
-
Define a task source for completing asynchronous events w3c/window-management#79.
-
Does window.getScreenDetails() always resolve with the same object? w3c/window-management#80.
-
-
7 issues received 12 new comments.
-
Provide Physical Dimensions / PPI of Displays w3c/window-management#65 (4 comments by @michaelwasserman, @seflless)
-
ScreenDetails defines "currentScreens" getter steps w3c/window-management#81 (2 comments by @michaelwasserman, @reillyeon)
-
Does window.getScreenDetails() always resolve with the same object? w3c/window-management#80 (2 comments by @michaelwasserman, @reillyeon)
-
Is ScreenDetails supposed to inherit from EventTarget? w3c/window-management#90 (1 comment by @michaelwasserman)
-
Add "window-placement" to Powerful Features Registry (rather than Permissions) w3c/window-management#89 (1 comment by @michaelwasserman)
-
Define a task source for completing asynchronous events w3c/window-management#79 (1 comment by @michaelwasserman)
-
-
3 pull requests opened.
-
Refine event firing steps w3c/window-management#88, by @michaelwasserman.
-
Refine spec concepts, terminology, prose, definitions, and algorithms. w3c/window-management#87, by @michaelwasserman.
-
Remove one more instance of `id` w3c/window-management#86, by @tomayac.
-
-
3 pull requests merged.
-
Refine event firing steps w3c/window-management#88.
-
Refine spec concepts, terminology, prose, definitions, and algorithms. w3c/window-management#87.
-
Remove one more instance of `id` w3c/window-management#86.
-
-
3 pull requests received 47 new comments.
-
Refine spec concepts, terminology, prose, definitions, and algorithms. w3c/window-management#87 (45 comments by @michaelwasserman, @reillyeon, @tomayac)
-
Past meetings
GitHub
w3c/window-management
-
7 issues opened.
-
Exposing content area coordinates w3c/window-management#84, by @michaelwasserman.
-
Fix spec language around "main dimension" and "secondary dimension". w3c/window-management#83, by @michaelwasserman.
-
ScreenDetails defines "currentScreens" getter steps w3c/window-management#81, by @reillyeon.
-
Does window.getScreenDetails() always resolve with the same object? w3c/window-management#80, by @reillyeon.
-
Define a task source for completing asynchronous events w3c/window-management#79, by @reillyeon.
-
Incorrect screen positions in "Virtual screen area" diagram w3c/window-management#77, by @reillyeon.
-
Question about multi screen spanning w3c/window-management#74, by @konorti.
-
-
3 issues closed.
-
Specify the order of returned screen objects w3c/window-management#19.
-
Fix spec language around "main dimension" and "secondary dimension". w3c/window-management#83.
-
Incorrect screen positions in "Virtual screen area" diagram w3c/window-management#77.
-
-
9 issues received 15 new comments.
-
Question about multi screen spanning w3c/window-management#74 (2 comments by @konorti, @michaelwasserman)
-
Provide Physical Dimensions / PPI of Displays w3c/window-management#65 (2 comments by @electronicwhisper, @seflless)
-
Does window.getScreenDetails() always resolve with the same object? w3c/window-management#80 (2 comments by @quisquous, @reillyeon)
-
ScreenDetails defines "currentScreens" getter steps w3c/window-management#81 (2 comments by @quisquous, @reillyeon)
-
Exposing content area coordinates w3c/window-management#84 (2 comments by @michaelwasserman, @quisquous)
-
Collecting Developer Feedback w3c/window-management#67 (2 comments by @michaelwasserman, @thomaschaaf)
-
Specify the order of returned screen objects w3c/window-management#19 (1 comment by @michaelwasserman)
-
Fix spec language around "main dimension" and "secondary dimension". w3c/window-management#83 (1 comment by @michaelwasserman)
-
Incorrect screen positions in "Virtual screen area" diagram w3c/window-management#77 (1 comment by @michaelwasserman)
-
-
5 pull requests opened.
-
Add a basic HOWTO.md w3c/window-management#85, by @michaelwasserman.
-
Fix the multi-screen origin image; embed svg and add psd source to repo. w3c/window-management#82, by @michaelwasserman.
-
Fix typo in description of internal screens w3c/window-management#78, by @reillyeon.
-
Fix the computation of window coordinates for a target screen w3c/window-management#76, by @michaelwasserman.
-
Write a simple usage overview w3c/window-management#75, by @michaelwasserman.
-
-
5 pull requests merged.
-
Add a basic HOWTO.md w3c/window-management#85.
-
Fix the computation of window coordinates for a target screen w3c/window-management#76.
-
Fix the multi-screen origin image; embed svg and add psd source to repo. w3c/window-management#82.
-
Fix typo in description of internal screens w3c/window-management#78.
-
Write a simple usage overview w3c/window-management#75.
-
-
3 pull requests received 15 new comments.
-
Fix the computation of window coordinates for a target screen w3c/window-management#76 (4 comments by @michaelwasserman, @reillyeon)
w3c/openscreenprotocol
-
2 issues received 3 new comments.
-
[Remote Playback] Capabilities for HDR rendering and display w3c/openscreenprotocol#194 (2 comments by @chrisn, @markafoltz)
-
-
2 pull requests opened.
-
Update pygmentize_dir.py for python3 w3c/openscreenprotocol#290, by @markafoltz.
-
Fix a couple of typos: no "format" field and audio/video mix-up w3c/openscreenprotocol#289, by @tidoust.
-
-
3 pull requests merged.
-
Reference Media Capabilities ColorGamut for color space capability w3c/openscreenprotocol#225.
-
Update pygmentize_dir.py for python3 w3c/openscreenprotocol#290.
-
Fix a couple of typos: no "format" field and audio/video mix-up w3c/openscreenprotocol#289.
-
-
1 pull request received 6 new comments.
-
Reference Media Capabilities ColorGamut for color space capability w3c/openscreenprotocol#225 (6 comments by @chcunningham, @markafoltz)
-
w3c/secondscreen-charter
-
1 issue closed.
-
fingerprinting mitigations for multi-screen window placement w3c/secondscreen-charter#26.
-
-
1 issue received 7 new comments.
-
fingerprinting mitigations for multi-screen window placement w3c/secondscreen-charter#26 (7 comments by @npdoty, @pes10k, @samuelweiler, @tidoust)
-
-
5 pull requests opened.
-
Update change history table w3c/secondscreen-charter#36, by @tidoust.
-
Add Media WG to coordination section w3c/secondscreen-charter#35, by @tidoust.
-
Minor tweaks for proposed charter 2022 w3c/secondscreen-charter#33, by @plehegar.
-
Add Matter's CSA in external organizations w3c/secondscreen-charter#31, by @tidoust.
-
Update ref to fingerprinting surface in success criteria w3c/secondscreen-charter#30, by @tidoust.
-
-
5 pull requests merged.
-
Update change history table w3c/secondscreen-charter#36.
-
Add Media WG to coordination section w3c/secondscreen-charter#35.
-
Minor tweaks for proposed charter 2022 w3c/secondscreen-charter#33.
-
Add Matter's CSA in external organizations w3c/secondscreen-charter#31.
-
Update ref to fingerprinting surface in success criteria w3c/secondscreen-charter#30.
-
-
2 pull requests received 5 new comments.
-
Add Matter's CSA in external organizations w3c/secondscreen-charter#31 (3 comments by @louaybassbouss, @markafoltz, @tidoust)
-
Update ref to fingerprinting surface in success criteria w3c/secondscreen-charter#30 (2 comments by @markafoltz, @tidoust)
-