@@ -101,15 +101,33 @@ Image Values: the <<image>> type {#image-values}
101
101
including the 'background-image' , 'list-style-image' , 'cursor' properties [[!CSS2]]
102
102
(where it replaces the <<url>> component in the property's value).
103
103
104
- In some cases, an image is invalid,
105
- such as a <<url>> pointing to a resource that is not a valid image format.
104
+ In some cases an image is invalid,
105
+ such as a <<url>> pointing to a resource that is not a valid image format
106
+ or that has failed to load.
106
107
An <dfn export lt="invalid image|valid image">invalid image</dfn> is rendered as a solid-color ''transparent'' image with no intrinsic dimensions.
107
108
However, <a>invalid images</a> can trigger error-handling clauses
108
109
in some contexts.
109
110
For example, an <a>invalid image</a> in 'list-style-image'
110
111
is treated as ''list-style-type/none'' ,
111
112
allowing the 'list-style-type' to render in its place. [[CSS2]]
112
113
114
+ While an image is loading,
115
+ is is a <dfn export>loading image</dfn> .
116
+ [=Loading images=] are <em> not</em> [=invalid images=] ,
117
+ but have similar behavior:
118
+ they are rendered as a solid-color ''transparent'' image with no intrinsic dimensions,
119
+ and may trigger fallback rendering in contexts that offer it,
120
+ but must not trigger loading of fallback resources.
121
+
122
+ Partially-loaded images (whose [=intrinsic dimensions=] are known, but whose image data is not fully loaded)
123
+ may be either treated as [=loading images=]
124
+ or as loaded images rendered with partial data.
125
+ For example, a UA may render an interlaced GIF in place
126
+ as soon as its first pass of pixel data has loaded
127
+ or even as soon as the image header (which contains sizing data) has parsed
128
+ and refresh the rendering as more data loads;
129
+ or it may wait until the entire image has loaded before using it.
130
+
113
131
<!--
114
132
██ ██ ██ ████████ ██ ██
115
133
██ ██ ██ ██ ██ ██ ██
0 commit comments