From e29e82925000cf82482a007ac54cbb7927923cd4 Mon Sep 17 00:00:00 2001 From: Kyle Williams Date: Sat, 12 Nov 2022 08:07:42 -0500 Subject: [PATCH 1/5] alt tag added for presentation_mode_illustration.png --- files/en-us/web/api/presentation_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/presentation_api/index.md b/files/en-us/web/api/presentation_api/index.md index 168a2f8ff7d5389..326b399ce8f52c5 100644 --- a/files/en-us/web/api/presentation_api/index.md +++ b/files/en-us/web/api/presentation_api/index.md @@ -15,7 +15,7 @@ browser-compat: api.Presentation The Presentation API lets a {{Glossary("user agent")}} (such as a Web browser) effectively display web content through large presentation devices such as projectors and network-connected televisions. Supported types of multimedia devices include both displays which are wired using HDMI, DVI, or the like, or wireless, using [DLNA](https://www.dlna.org/), [Chromecast](https://developers.google.com/cast/), [AirPlay](https://developer.apple.com/airplay/), or [Miracast](https://www.wi-fi.org/discover-wi-fi/miracast). -![](presentation_mode_illustration.png) +![1-UA mode loaded the Controlling and Presenting pages together before outputting to displays. 2-UA mode loaded them separately using the Presentation Control Protocol.](presentation_mode_illustration.png) In general, a web page uses the Presentation Controller API to specify the web content to be rendered on presentation device and initiate the presentation session. With Presentation Receiver API, the presenting web content obtains the session status. With providing both the controller page and the receiver one with a messaged-based channel, a Web developer can implement the interaction between these two pages. From 33e98a34d339a97756c056203a2e998ff0dec09f Mon Sep 17 00:00:00 2001 From: Kyle Williams Date: Sat, 12 Nov 2022 08:25:23 -0500 Subject: [PATCH 2/5] reverting to b713a31399 --- files/en-us/web/api/presentation_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/presentation_api/index.md b/files/en-us/web/api/presentation_api/index.md index 326b399ce8f52c5..168a2f8ff7d5389 100644 --- a/files/en-us/web/api/presentation_api/index.md +++ b/files/en-us/web/api/presentation_api/index.md @@ -15,7 +15,7 @@ browser-compat: api.Presentation The Presentation API lets a {{Glossary("user agent")}} (such as a Web browser) effectively display web content through large presentation devices such as projectors and network-connected televisions. Supported types of multimedia devices include both displays which are wired using HDMI, DVI, or the like, or wireless, using [DLNA](https://www.dlna.org/), [Chromecast](https://developers.google.com/cast/), [AirPlay](https://developer.apple.com/airplay/), or [Miracast](https://www.wi-fi.org/discover-wi-fi/miracast). -![1-UA mode loaded the Controlling and Presenting pages together before outputting to displays. 2-UA mode loaded them separately using the Presentation Control Protocol.](presentation_mode_illustration.png) +![](presentation_mode_illustration.png) In general, a web page uses the Presentation Controller API to specify the web content to be rendered on presentation device and initiate the presentation session. With Presentation Receiver API, the presenting web content obtains the session status. With providing both the controller page and the receiver one with a messaged-based channel, a Web developer can implement the interaction between these two pages. From 40169d6b64644770bccc17c00a42b9fd1ab37bdb Mon Sep 17 00:00:00 2001 From: Kyle Williams Date: Sat, 12 Nov 2022 08:27:08 -0500 Subject: [PATCH 3/5] added alt tag -> presentation_mode_illustration.png --- files/en-us/web/api/presentation_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/presentation_api/index.md b/files/en-us/web/api/presentation_api/index.md index 168a2f8ff7d5389..326b399ce8f52c5 100644 --- a/files/en-us/web/api/presentation_api/index.md +++ b/files/en-us/web/api/presentation_api/index.md @@ -15,7 +15,7 @@ browser-compat: api.Presentation The Presentation API lets a {{Glossary("user agent")}} (such as a Web browser) effectively display web content through large presentation devices such as projectors and network-connected televisions. Supported types of multimedia devices include both displays which are wired using HDMI, DVI, or the like, or wireless, using [DLNA](https://www.dlna.org/), [Chromecast](https://developers.google.com/cast/), [AirPlay](https://developer.apple.com/airplay/), or [Miracast](https://www.wi-fi.org/discover-wi-fi/miracast). -![](presentation_mode_illustration.png) +![1-UA mode loaded the Controlling and Presenting pages together before outputting to displays. 2-UA mode loaded them separately using the Presentation Control Protocol.](presentation_mode_illustration.png) In general, a web page uses the Presentation Controller API to specify the web content to be rendered on presentation device and initiate the presentation session. With Presentation Receiver API, the presenting web content obtains the session status. With providing both the controller page and the receiver one with a messaged-based channel, a Web developer can implement the interaction between these two pages. From 9aef908f3687913323760760a114d35c275055cf Mon Sep 17 00:00:00 2001 From: Kyle Williams Date: Mon, 14 Nov 2022 08:56:12 -0500 Subject: [PATCH 4/5] removed alt tag from presentation_mode_illustration.png on main branch --- files/en-us/web/api/presentation_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/presentation_api/index.md b/files/en-us/web/api/presentation_api/index.md index 326b399ce8f52c5..168a2f8ff7d5389 100644 --- a/files/en-us/web/api/presentation_api/index.md +++ b/files/en-us/web/api/presentation_api/index.md @@ -15,7 +15,7 @@ browser-compat: api.Presentation The Presentation API lets a {{Glossary("user agent")}} (such as a Web browser) effectively display web content through large presentation devices such as projectors and network-connected televisions. Supported types of multimedia devices include both displays which are wired using HDMI, DVI, or the like, or wireless, using [DLNA](https://www.dlna.org/), [Chromecast](https://developers.google.com/cast/), [AirPlay](https://developer.apple.com/airplay/), or [Miracast](https://www.wi-fi.org/discover-wi-fi/miracast). -![1-UA mode loaded the Controlling and Presenting pages together before outputting to displays. 2-UA mode loaded them separately using the Presentation Control Protocol.](presentation_mode_illustration.png) +![](presentation_mode_illustration.png) In general, a web page uses the Presentation Controller API to specify the web content to be rendered on presentation device and initiate the presentation session. With Presentation Receiver API, the presenting web content obtains the session status. With providing both the controller page and the receiver one with a messaged-based channel, a Web developer can implement the interaction between these two pages. From a45ba11cb005bcd455c155c6b415bf37a30bf9a6 Mon Sep 17 00:00:00 2001 From: Kyle Williams Date: Mon, 12 Dec 2022 10:41:22 -0500 Subject: [PATCH 5/5] added alt tag for stereopannernode.png --- files/en-us/web/api/stereopannernode/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/stereopannernode/index.md b/files/en-us/web/api/stereopannernode/index.md index eb77c575cc0418f..dfc3e69ca1b71c6 100644 --- a/files/en-us/web/api/stereopannernode/index.md +++ b/files/en-us/web/api/stereopannernode/index.md @@ -18,7 +18,7 @@ The `StereoPannerNode` interface of the [Web Audio API](/en-US/docs/Web/API/Web_ The {{domxref("StereoPannerNode.pan", "pan")}} property takes a unitless value between `-1` (full left pan) and `1` (full right pan). This interface was introduced as a much simpler way to apply a simple panning effect than having to use a full {{domxref("PannerNode")}}. -![](stereopannernode.png) +![The Stereo Panner Node moved the sound's position from the center of two speakers to the left.](stereopannernode.png) {{InheritanceDiagram}}