Closed: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Pull Request: Addresses Issue #394: Reject start() in all browsing contexts
[presentation-api] Pull Request: Adds a note about display of origins that are not potentially trustworthy.
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Pull Request: Addresses Issue #391
[presentation-api] Pull Request: Addresses Issue #398: Sandboxing steps in start, reconnect, getAvailability are now useless
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless
- Re: [presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless
- Closed: [presentation-api] Sandboxing steps in start, reconnect, getAvailability are now useless
[presentation-api] Make sure all IDL members have "dfn" in prose
Re: [presentation-api] [meta] Presentation API Testing
Re: [presentation-api] Well defined environment for nested contexts of the receiving browsing context?
Closed: [presentation-api] Well defined environment for nested contexts of the receiving browsing context?
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Migrate HTML 5.0 references to HTML 5.1?
[presentation-api] Pull Request: Addreses Issue 387
[presentation-api] Make select algo reject in ancestor and descendant browsing contexts
- Re: [presentation-api] Make select algo reject in ancestor and descendant browsing contexts
- Closed: [presentation-api] Make select algo reject in ancestor and descendant browsing contexts
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Pull Request: Rename PresentationConnectionClosedReason to PresentationConnectionCloseReason
[presentation-api] Pull Request: Issue #387: Monitoring algo takes pending request to start into account
- Re: [presentation-api] Issue #387: Monitoring algo takes pending request to start into account
- Re: [presentation-api] Issue #387: Monitoring algo takes pending request to start into account
- Re: [presentation-api] Issue #387: Monitoring algo takes pending request to start into account
Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts
- Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts
- Re: [presentation-api] Authenticity of screen selection permission is problematic in insecure contexts
[presentation-api] Steps that re-use objects should specify the relevant settings object/Javascript Realm
Closed: [presentation-api] Clarify event order when establishing a presentation connection
[presentation-api] new commits pushed by mfoltzgoogle
Re: [remote-playback] Internationalization considerations
[presentation-api] Pull Request: Issue 387: Need to make sure we have a display list for start().
- Re: [presentation-api] Issue 387: Need to make sure we have a display list for start().
- Re: [presentation-api] Issue 387: Need to make sure we have a display list for start().
- Re: [presentation-api] Issue 387: Need to make sure we have a display list for start().
- Re: [presentation-api] Issue 387: Need to make sure we have a display list for start().
- Re: [presentation-api] Issue 387: Need to make sure we have a display list for start().
[presentation-api] Pull Request: Issue #360: Adds a presentation task source
Closed: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor
[presentation-api] new commits pushed by mfoltzgoogle
Closed: [presentation-api] Determine if we need to fire a terminated event in the receiving browsing context(s)
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] new commits pushed by mfoltzgoogle
[presentation-api] Check on Presentation display availability in getAvailability can never be true
- Re: [presentation-api] Check on Presentation display availability in getAvailability can never be true
- Re: [presentation-api] Check on Presentation display availability in getAvailability can never be true
- Re: [presentation-api] Check on Presentation display availability in getAvailability can never be true
- Re: [presentation-api] Check on Presentation display availability in getAvailability can never be true
- Re: [presentation-api] Check on Presentation display availability in getAvailability can never be true
- Closed: [presentation-api] Check on Presentation display availability in getAvailability can never be true
[presentation-api] Filling out the list of available presentation displays for start
- Re: [presentation-api] Filling out the list of available presentation displays for start
- Re: [presentation-api] Filling out the list of available presentation displays for start
- Re: [presentation-api] Filling out the list of available presentation displays for start
- Closed: [presentation-api] Filling out the list of available presentation displays for start
[presentation-api] Pull Request: Sets the state of receiving presentation connections to terminated before unload.
[presentation-api] Pull Request: Issue #379: Adds sandboxing flag check to PresentationRequest ctor.
Re: [presentation-api] Investigate if sandboxing flag check can move to the PresentationRequest ctor
[presentation-api] Pull Request: Addresses Issues 382 and 383 on the steps to get presentation displays.
- Re: [presentation-api] Addresses Issues 382 and 383 on the steps to get presentation displays.
- Re: [presentation-api] Addresses Issues 382 and 383 on the steps to get presentation displays.
[presentation-api] Step 11 of getAvailability should not run "in parallel"
- Re: [presentation-api] Step 11 of getAvailability should not run "in parallel"
- Re: [presentation-api] Step 11 of getAvailability should not run "in parallel"
- Re: [presentation-api] Step 11 of getAvailability should not run "in parallel"
- Re: [presentation-api] Step 11 of getAvailability should not run "in parallel"
- Closed: [presentation-api] Step 11 of getAvailability should not run "in parallel"
- Re: [presentation-api] Step 11 of getAvailability should not run "in parallel"
[presentation-api] Drop step 6 of getAvailability for consistency with start?
- Re: [presentation-api] Drop step 6 of getAvailability for consistency with start?
- Closed: [presentation-api] Drop step 6 of getAvailability for consistency with start?
[presentation-api] Wrong use of "available presentation displays" in 6.4.4
- Re: [presentation-api] Wrong use of "available presentation displays" in 6.4.4
- Closed: [presentation-api] Wrong use of "available presentation displays" in 6.4.4