From 987365041fcd1e7e4342077ddf6fe5cadd1da688 Mon Sep 17 00:00:00 2001 From: Barb Paduch Date: Fri, 16 Sep 2016 18:53:17 -0400 Subject: [PATCH] Add references to layout docs; fixes #173 (#5063) --- builtins/amp-img.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builtins/amp-img.md b/builtins/amp-img.md index 406df9bef513..b14885343fd1 100644 --- a/builtins/amp-img.md +++ b/builtins/amp-img.md @@ -40,7 +40,7 @@ limitations under the License. The runtime may choose to delay or prioritize resource loading based on the viewport position, system resources, connection bandwidth, or other factors. The `amp-img` components allows the runtime to effectively manage image resources this way. `amp-img` components, like all externally fetched AMP resources, must be given an -explicit size (as in width / height) in advance, so that the aspect ratio can be known without fetching the image. Actual layout behavior is determined by the layout attribute. +explicit size (as in width / height) in advance, so that the aspect ratio can be known without fetching the image. Actual layout behavior is determined by the layout attribute. For details on layouts, see [AMP HTML Layout System](https://github.com/ampproject/amphtml/blob/master/spec/amp-html-layout.md) and [Supported Layouts](https://www.ampproject.org/docs/guides/responsive/control_layout.html). If the resource requested by the `amp-img` component fails to load, the space will be blank unless a [`fallback`](https://github.com/ampproject/amphtml/blob/master/spec/amp-html-layout.md#fallback) child is provided. A fallback is only executed on the initial layout and subsequent src changes after the fact (through resize + srcset for example) will not have a fallback for performance implications.