While the site author could support this in a very rudimentary way (e.g. Rather than mirroring the presentation onto a remote endpoint, the user really wants to present the slides full-screen on the projector, leaving the laptop screen available for speaker notes and slide control. For example, imagine a user in a conference room outfitted with a projector to which they are connected via an HDMI cable. There are scenarios though where users may simply want to present content onto a second, attached display. Examples include managing a playback queue on while videos play on the TV, or seeing a slide reel with speaker notes on a laptop while the fullscreen presentation is shown in a Hangout session. Until now, web developers could build experiences where a user would see local content in Chrome that is different from the content they’d see on a remote display while still being able to control that experience locally. A web page is automatically presented to the display previously picked # Background User picks a secondary attached display alt="Step 2"/> 2/2. Chrome 66 allows web pages to use a secondary attached display through the Presentation API and to control its contents through the Presentation Receiver API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |