presentation-api
presentation-api copied to clipboard
w3c
Presentation API
In the future we should discuss how to update the spec language to account for the fact that since the spec was written, there are new ways for documents to...
This is related to Issue #347. It would be ergonomic to allow objects accessible to the developer to be presentable on other devices via object URLs or source objects. This...
Currently the Presentation API can only present fully fledged documents which are loaded in a separate (and isolated) browsing context. There may be use cases where it is not possible...
This proposal adds a friendly name (e.g. "Living Room TV") attribute to the `PresentationReceiver` interface. #467 adds the same to `PresentationConnection` on the controller side. *** Preview | Diff
This is a proposal to add a receiver name attribute to `PresentationConnection` on the controlling UA side. `receiverName` is the friendly name of the presentation display associated with the presentation...
The Presentation API assumes that the user agent handles the discovery, control and the establishment of the communication channel. In issue #61 (Add facility for the opening page to add...
This is a spec issue raised by the Open Screen Protocol. There's support in the protocol for reconnecting to a presentation, but no step in the Presentation API indicating when...
We should understand the constraints that a possible compatibility with HbbTV could put on the design of the Presentation API. Related discussion at: https://lists.w3.org/Archives/Public/public-secondscreen/2015Feb/0102.html
It's possible for Web applications to add custom HTTP headers, i.e. for authentication, to resource fetch requests. We have an internal application that is looking to load an authenticated page...
**Problem:** Presentation API and Remote Playback API each has a method to start a session, namely `PresentationRequest.start()` and `RemotePlayback.prompt()`. Each shows a potentially different list of receiver devices to choose...