@@ -216,7 +216,7 @@ Image References: the ''url()'' notation {#url-notation}
216216### Image Metadata ### {#url-metadata}
217217
218218Images can contain metadata
219- such as resolution and orientation
219+ such as color space, resolution and orientation
220220which specifies how to render the image.
221221Some image formats are flexible in where this metadata can be placed in the file;
222222however, if the metadata occurs <em> after</em> the actual image data,
@@ -226,21 +226,19 @@ and display it as the image's data streams in.
226226To reduce the impact of this issue:
227227
228228* If the choice exists for a given image format,
229- authors <em> must</em> produce their image files
230- so that such metadata occurs before the image data in the image file .
229+ authors <em> must</em> produce their images
230+ so that such metadata occurs before the image data in the image.
231231 (Note: This is the default for most images already.)
232232* User agents <em> should</em> ignore any layout-impacting metadata (such as orientation or resolution)
233- that occurs after the image data begins in the file.
234- (Note: This rule does not impact metadata that does not affect layout,
235- such as color space information.)
233+ that occurs after the image data begins.
236234
237- If a user agent cannot ignore the metadata based its location in the file
235+ If a user agent cannot ignore the metadata based its location in the image
238236 (for example, if the decoder being used
239- does not report where in the file the metadata was located),
237+ does not report where in the image the metadata was located),
240238 it <em> must</em> use the metadata in all cases.
241239 (In particular, it is not valid
242240 to use the metadata only when the image is "small"
243- and the entire file is downloaded quickly,
241+ and the entire image is downloaded quickly,
244242 but to ignore it if the image is large
245243 and the metadata isn't downloaded until well after the image starts being displayed.)
246244
0 commit comments