CSS Images Module Level 4

1. Introduction

This section is not normative.

This module introduces additional ways of representing 2D images, for example as a URL with color fallback, as conic gradients, or as the rendering of another element in the document.

1.1. Value Definitions

This specification follows the CSS property definition conventions from [CSS2] using the value definition syntax from [CSS-VALUES-3]. Value types not defined in this specification are defined in CSS Values & Units [CSS-VALUES-3]. Combination with other CSS modules may expand the definitions of these value types.

In addition to the property-specific values listed in their definitions, all properties defined in this specification also accept the CSS-wide keywords as their property value. For readability they have not been repeated explicitly.

2. 2D Image Values: the <image> type

The <image> value type denotes a 2D image. It can be a url reference, image notation, or gradient notation. Its syntax is:

<image> = <url> | <image()> | <image-set()> | <cross-fade()> | <element()> | <gradient>

An <image> can be used in many CSS properties, including the background-image, list-style-image, cursor properties [CSS2] (where it replaces the <url> component in the property’s value).

In some cases an image is invalid, such as a <url> pointing to a resource that is not a valid image format or that has failed to load. An invalid image is rendered as a solid-color transparent image with no natural dimensions. However, invalid images can trigger error-handling clauses in some contexts. For example, an invalid image in list-style-image it is treated as none, allowing the list-style-type to render in its place. [CSS2]

While an image is loading, is a loading image. Loading images are not invalid images, but have similar behavior: they are rendered as a solid-color transparent image with no natural dimensions, and may trigger fallback rendering in contexts that offer it, but must not trigger loading of fallback resources. Alternately, if a loading image happens to be replacing an already-loaded image (for example due to changes in the document or style sheet) and the UA is tracking this information, it may continue to render the already-loaded image in place of the loading image.

Partially-loaded images (whose natural dimensions are known, but whose image data is not fully loaded) may be either treated as loading images or as loaded images rendered with partial data. For example, a UA may render an interlaced GIF in place as soon as its first pass of pixel data has loaded or even as soon as the image header (which contains sizing data) has parsed and refresh the rendering as more data loads; or it may wait until the entire image has loaded before using it.

A computed <image> value is the specified value with any <url>s, <color>s, and <length>s computed.

2.1. Image File Formats

At minimum, the UA must support the following image file formats when referenced from an <image> value, for all the properties in which using <image> is valid:

• PNG, as specified in [PNG]
• SVG, as specified in [SVG11], using the secure static mode (See [SVG-INTEGRATION])
• If the UA supports animated <image>s, SVG, as specified in [SVG11], using the secure animated mode (See [SVG-INTEGRATION])

The UA may support other file formats as well.

2.2. Image References: the url() notation

Note: No change from [css3-images].

2.3. Fetching External Images

2.4. Resolution/Type Negotiation: the image-set() notation

Delivering the most appropriate image resolution for a user’s device can be a difficult task. Ideally, images should be in the same resolution as the device they’re being viewed in, which can vary between users. However, other factors can factor into the decision of which image to send; for example, if the user is on a slow mobile connection, they may prefer to receive lower-res images rather than waiting for a large proper-res image to load. The image-set() function allows an author to ignore most of these issues, simply providing multiple resolutions of an image and letting the UA decide which is most appropriate in a given situation.

This solution assumes that resolution is a proxy for filesize, and therefore doesn’t appropriately handle multi-resolution sets of vector images, or mixing vector images with raster ones (e.g. for icons). For example, use a vector for high-res, pixel-optimized bitmap for low-res, and same vector again for low-bandwidth (because it’s much smaller, even though it’s higher resolution).

The syntax for image-set() is:

image-set() = image-set( <image-set-option># )
<image-set-option> = [ <image> | <string> ]
                     [ <resolution> || type(<string>) ]

We should add "w" and "h" dimensions as a possibility to match the functionality of HTML’s picture.

Each <string> inside image-set() represents a <url>.

The image-set() function can not be nested inside of itself, either directly or indirectly (as an argument to another <image> type).

Each <image-set-option> defines a possible image for the image-set() function to represent, composed of three parts:

• An image reference (required). This can be a URL, or a CSS generated image, such as a linear-gradient().

• A <resolution> (optional). This is used to help the UA decide which <image-set-option> to choose. If the image reference is for a raster image, it also specifies the image’s natural resolution, overriding any other source of data that might supply a natural resolution.

  If not specified, it behaves as 1x for the purpose of selecting which <image-set-option> to use. It also defaults the image’s natural resolution to 1x, but if some other source of data supplies a natural resolution, that resolution must be honored instead.

• A type( <string> ) function (optional), specifying the image’s MIME type in the <string>.

  If the <string>, when parsed as a valid MIME type string, is either not valid, or is valid but doesn’t specify a supported image format, the <image-set-option> does not define a valid option. (This has no effect on the validity of the image-set() function.)

  It does not have any effect on the image itself; an <image-set-option> like url("picture.png") 1x type("image/jpeg") is valid, and if chosen will display the linked PNG image, even though it was declared to be a JPEG.

  If not specified, it has no effect on the <image-set-option>.

An image-set() function contains a list of one or more <image-set-option>s, and must select only one of them to determine what image it will represent:

1. First, remove any <image-set-option>s from the list that specify an unknown or unsupported MIME type in their type() value.

2. Second, remove any <image-set-option>s from the list that have the same <resolution> as a previous option in the list.

3. Finally, among the remaining <image-set-option>s, make a UA-specific choice of which to load, based on whatever criteria deemed relevant (such as the resolution of the display, connection speed, etc).

4. The image-set() function then represents the <image> of the chosen <image-set-option>.

UAs may change which <image-set-option> they wish to use for a given image-set() over the lifetime of the page, if the criteria used to determine which option to choose change significantly enough to make it worthwhile in the UA’s estimation.

background-image: image-set( "foo.png" 1x,
                             "foo-2x.png" 2x,
                             "foo-print.png" 600dpi );

background-image: image-set( "foo.avif" type("image/avif"),
                             "foo.jpg" type("image/jpeg") );

background-image: image-set( linear-gradient(cornflowerblue, white) 1x,
                             url("detailed-gradient.png") 3x );

2.5. Image Fallbacks and Annotations: the image() notation

The image() function allows an author to:

• use media fragments to clip out a portion of an image

• use a solid color as an image

• fallback to a solid-color image, when the image at the specified url can’t be downloaded or decoded

• automatically respect the image orientation specified in the image’s metadata

The image() notation is defined as:

image() = image( <image-tags>? [ <image-src>? , <color>? ]! )
<image-tags> = [ ltr | rtl ]
<image-src> = [ <url> | <string> ]

A <string> used in image() represents a <url>. As usual for URLs in CSS, relative URLs are resolved to an absolute URL (as described in Values & Units [CSS-VALUES-3]) when a specified image() value is computed.

If the image has an orientation specified in its metadata, such as EXIF, the UA must rotate or flip the image to correctly orient it as the metadata specifies.

2.5.1. Image Fallbacks

If both a URL and a <color> are specified in image(), then whenever the URL represents an invalid image or loading image, the image() function renders as if the URL were not specified at all; it generates a solid-color image as specified in § 2.5.3 Solid-color Images.

If just a URL is specified (no <color>) and it represents an invalid image or loading image, the image() function represents the same.

body      { color: black; background: white; }
p.special { color: white; background: url("dark.png") black; }

body      { color: black; background: white; }
p.special { color: white; background: image("dark.png", black); }

2.5.2. Image Fragments

When a URL specified in image() represents a portion of a resource (e.g. by the use of media fragment identifiers) that portion is clipped out of its context and used as a standalone image.

background-image: image('sprites.svg#xywh=40,0,20,20')

So that authors can take advantage of CSS’s forwards-compatible parsing rules to provide a fallback for image slices, implementations that support the image() notation must support the xywh=#,#,#,# form of media fragment identifiers for images specified via image(). [MEDIA-FRAGS]

background-image: url('swirl.png'); /* old UAs */
background-image: image('sprites.png#xywh=10,30,60,20'); /* new UAs */

If a URL uses a fragment identifier syntax that the implementation does not understand, or does not consider valid for that type of image, the URL must be treated as representing an invalid image.

Note: This error-handling is limited to image(), and not in the definition of URL, for legacy compat reasons.

2.5.3. Solid-color Images

If the image() function is specified with only a <color> argument (no URL), it represents a solid-color image of the specified color with no natural dimensions.

background-image: image(rgba(0,0,255,.5)), url("bg-image.png");

2.5.4. Bidi-sensitive Images

Before listing any <image-src>s, the author may specify a directionality for the image, similar to adding a dir attribute to an element in HTML. If a directional image is used on or in an element with opposite direction, the image must be flipped in the inline direction (as if it was transformed by, e.g., scaleX(-1), if the inline direction is the X axis).

Note: Absent this declaration, images default to no directionality at all, and thus don’t care about the directionality of the surrounding element.

<ul style="list-style-image: image(ltr 'arrow.png');">
  <li dir='ltr'>My bullet is on the left!</li>
  <li dir='rtl'>MY BULLET IS ON THE RIGHT!</li>
</ul>

⇒ My bullet is on the left!
  !THGIR EHT NO SI TELLUB YM ⇐

2.6. Combining images: the cross-fade() notation

When transitioning between images, CSS requires a way to explicitly refer to the intermediate image that is a combination of the start and end images. This is accomplished with the cross-fade() function, which indicates the two images to be combined and how far along in the transition the combination is.

Note: Authors can also use the cross-fade() function for many simple image manipulations, such as tinting an image with a solid color or highlighting a particular area of the page by combining an image with a radial gradient.

The syntax for cross-fade() is defined as:

cross-fade() = cross-fade( <cf-image># )
<cf-image> = <percentage [0,100]>? && [ <image> | <color> ]

The function represents an image generated by combining two or more images.

The <percentage> represents how much of each image is retained when it is blended with the other images. The <percentage> must be between 0% and 100% inclusive; any other value is invalid.

If any percentages are omitted, all the specified percentages are summed together and subtracted from 100%, the result is floored at 0%, then divided equally between all images with omitted percentages at computed-value time.

If a <color> is provided, it represents a solid-color image with “automatic” dimensions (it doesn’t participate in the sizing of the result image at all; see details in the sizing details below).

2.6.1. cross-fade() Sizing

The dimensions of the image represented by a cross-fade() are a weighted average of dimensions of the <image> arguments to the function; the <color> arguments have no effect. They are calculated as follows:

2.6.2. cross-fade() Painting

The image represented by a cross-fade() is a weighted average of the input arguments to the function, calculated as follows:

2.6.3. Simplifying Complex cross-fade()

Per WG resolution, define a notion of "equality" for images, and combine "same" images at computed-value time, summing their percentages.

Per WG resolution, simplify directly-nested cross-fade() at computed-value time by just distributing the percentage and flattening; cross-fade(A 10%, cross-fade(B 30%, C 70%) 90%) becomes cross-fade(A 10%, B 27%, C 63%).

2.7. Using Elements as Images: the element() notation

The element() function allows an author to use an element in the document as an image. As the referenced element changes appearance, the image changes as well. This can be used, for example, to create live previews of the next/previous slide in a slideshow, or to reference a canvas element for a fancy generated gradient or even an animated background.

Note: The element() function only reproduces the appearance of the referenced element, not the actual content and its structure. Authors should only use this for decorative purposes, and must not use element() to reproduce an element with significant content across the page. Instead, just insert multiple copies of the element into the document.

The syntax for element() is:

element() = element( <id-selector> )

where <id-selector> is an ID selector [SELECT].

Do we need to be able to refer to elements in external documents (such as SVG paint servers)? Or is it enough to just use url() for this?

This name conflicts with a somewhat similar function in GCPM. This needs to be resolved somehow.

Want the ability to do "reflections" of an element, either as a background-image on the element or in a pseudo-element. This needs to be specially-handled to avoid triggering the cycle-detection.

When we have overflow:paged, how can we address a single page in the view?

The element() function references the element matched by its argument. The ID is first looked up in the elementSources map, as described in that section. If it’s not found, it’s then matched against the document. If multiple elements are matched, the function references the first such element.

The image represented by the element() function can vary based on whether the element is visible in the document:

an element that is rendered, is not a descendant of a replaced element, and generates a stacking context

The function represents an image with its natural size equal to the decorated bounding box of the referenced element:

• for an element rendered using a CSS rendering model, the decorated bounding box is the smallest axis-aligned rectangle that contains the border image areas of all the fragments of the principal box
• for an element rendered using the SVG rendering model, the decorated bounding box is defined by SVG

Note: Because images clip anything outside their bounds by default, this means that decorations that extend outside the decorated bounding box, like box shadows, may be clipped.

The image is constructed by rendering the referenced element and its descendants (at the same size that they would be in the document) over an infinite transparent canvas, positioned so that the edges of the decorated bounding box are flush with the edges of the image.

Requiring some degree of stacking context on the element appears to be required for an efficient implementation. Do we need a full stacking context, or just a pseudo-stacking context? Should it need to be a stacking context normally, or can we just render it as a stacking context when rendering it to element()?

If the referenced element has a transform applied to it or an ancestor, the transform must be ignored when rendering the element as an image. [CSS3-TRANSFORMS]

If the referenced element is broken across pages, the element is displayed as if the page content areas were joined flush in the pagination direction, with pages' edges corresponding to the initial containing block’s start edge aligned. Elements broken across lines or columns are just rendered with their decorated bounding box.

Implementations may either re-use existing bitmap data generated for the referenced element or regenerate the display of the element to maximize quality at the image’s size (for example, if the implementation detects that the referenced element is an SVG fragment); in the latter case, the layout of the referenced element in the image must not be changed by the regeneration process. That is, the image must look identical to the referenced element, modulo rasterization quality.

As a somewhat silly example, a p element can be reused as a background elsewhere in the document:

<style>
#src { color: white; background: lime; width: 300px; height: 40px; position: relative; }
#dst { color: black; background: element(#src); padding: 20px; margin: 20px 0; }
</style>
<p id='src'>I’m an ordinary element!</p>
<p id='dst'>I’m using the previous element as my background!</p>

an element that is not rendered, but which provides a paint source

The function represents an image with the natural dimensions and appearance of the paint source. The host language defines the size and appearance of paint sources.

For example, the element() function can reference an SVG <pattern> element in an HTML document:

<!DOCTYPE html>
<svg>
  <defs>
    <pattern id='pattern1'>
      <path d='...'>
    </pattern>
  </defs>
</svg>
<p style="background: element(#pattern1)">
  I’m using the pattern as a background!
  If the pattern is changed or animated,
  my background will be updated too!
</p>

HTML also defines that a handful of elements, such as canvas, img, and video, provide a paint source. This means that CSS can, for example, reference a canvas that’s being drawn into, but not displayed in the page:

<!DOCTYPE html>
<script>
  var canvas = document.querySelector('#animated-bullet');
  canvas.width = 20; canvas.height = 20;
  drawAnimation(canvas);
</script>
<canvas id='animated-bullet' style='display:none'></canvas>
<ul style="list-style-image: element(#animated-bullet);">
  <li>I’m using the canvas as a bullet!</li>
  <li>So am I!</li>
  <li>As the canvas is changed over time with Javascript,
      we’ll all update our bullet image with it!</li>
</ul>

anything else

The function represents an invalid image.

For example, all of the following element() uses will result in a transparent background:

<!DOCTYPE html>
<p id='one' style="display:none; position: relative;">one</p>
<iframe src="http://example.com">
  <p id='two' style="position: relative;">I’m fallback content!</p>
</iframe>
<ul>
  <li style="background: element(#one);">
    A display:none element isn’t rendered, and a P element
    doesn’t provide a paint source.
  </li>
  <li style="background: element(#two);">
    The descendants of a replaced element like an IFRAME
    can’t be used in element() either.
  </li>
  <li style="background: element(#three);">
    There’s no element with an id of "three", so this also
    gets rendered as a transparent image.
  </li>
</ul>

An element is not rendered if it does not have an associated box. This can happen, for example, if the element or an ancestor is display:none. Host languages may define additional ways in which an element can be considered not rendered; for example, in SVG, any descendant of a <defs> element is considered to be not rendered.

<!DOCTYPE html>
<script>
function navigateSlides() {
  var currentSlide = ...;
  document.querySelector('#prev-slide').id = '';
  document.querySelector('#next-slide').id = '';
  currentSlide.previousElementSibling.id = 'prev-slide';
  currentSlide.nextElementSibling.id = 'next-slide';
}
</script>
<style>
.slide {
  /* Need to be a stacking context to be element()-able. */
  position: relative;
}
#prev-preview, #next-preview {
  position: fixed;
  ...
}
#prev-preview { background: element(#prev-slide); }
#next-preview { background: element(#next-slide); }
</style>
<a id='prev-preview'>Previous Slide</a>
<a id='next-preview'>Next Slide</a>
<section class='slide'>...</section>
<section class='slide current-slide'>...</section>
...

2.7.1. Paint Sources

Host languages may define that some elements provide a paint source. Paint sources have an intrinsic appearance and can obtain a concrete object size without having to do layout or rendering, and so may be used as images even when they’re not rendered.

In HTML, the img, video, and canvas elements provide paint sources.

In SVG, any element that provides a paint server provides a paint source. Note: In SVG1.1, the <linearGradient>, <radialGradient>, and <pattern> elements provide paint sources. They are drawn as described in the spec, with the coordinate systems defined as follows:

objectBoundingBox

The coordinate system has its origin at the top left corner of the rectangle defined by the concrete object size that it’s being drawn into, and the same width and height as the concrete object size. A single user coordinate is the width and height of the concrete object size.

userSpaceOnUse

The coordinate system has its origin at the top left corner of the rectangle defined by the concrete object size that it’s being drawn into, and the same width and height as the concrete object size. User coordinates are sized equivalently to the CSS px unit.

Note: It is expected that a future version of this module will define ways to refer to paint sources in external documents, or ones that are created solely by script and never inserted into a document at all.

2.7.2. Using Out-Of-Document Sources: the ElementSources interface

The element() function normally selects elements within a document, but elements that provide a paint source don’t necessarily need to be in-document. For example, an HTML canvas element can be created, maintained, and drawn into entirely in script, with no need for it to be inserted into the document directly.

All that’s needed is a way to refer to the element, as an ID selector cannot select elements outside of the document. The elementSources Map object provides this.

partial namespace CSS {
  [SameObject] readonly attribute any elementSources;
};

Any entries in the elementSources map with a string key and a value that is an object providing a paint source are made available to the element() function.

Whenever element() uses an <id-selector>, the ID’s value (without the leading # character) is first looked up in the elementSources map:

• If it’s found, and the object associated with it provides a paint source, the element() function represents that paint source.
• If it’s found, but the object associated with it doesn’t provide a paint source, the element() function represent an invalid image.
• If the ID isn’t found in the map at all, it’s then looked for in the document as normal.

This reuse of the ID selector matches Moz behavior. I’m trying to avoid slapping a <custom-ident> right in the beginning of the grammar, as that eats too much syntax-space. Another possibility, though, is to start the value with a language-defined keyword followed by a <custom-ident>, like element(external fancy) or something. Naming suggestions welcome.

<script>
var bg = document.createElement('canvas');
bg.height = 200;
bg.width = 1000;
drawFancyBackground(bg);
CSS.elementSources.set('fancy', bg);
</script>
<style>
h1 {
  background-image: element(#fancy);
}
</style>

2.7.3. Cycle Detection

The element() function can produce nonsensical circular relationships, such as an element using itself as its own background. These relationships can be easily and reliably detected and resolved, however, by keeping track of a dependency graph and using common cycle-detection algorithms.

The dependency graph consists of edges such that:

• every element depends on its children
• for any element A with a property using the element() function pointing to an element B, A depends on B
• if a host language defines a way for elements to refer to the rendering of other elements, the referencing element depends on the referenced element. For example, in SVG, a <use> element depends on the element it referenced.

If the graph contains a cycle, any element() functions participating in the cycle are invalid images.

3. Gradients

A gradient is an image that smoothly fades from one color to another. These are commonly used for subtle shading in background images, buttons, and many other things. The gradient functions described in this section allow an author to specify such an image in a terse syntax, so that the UA can generate the image automatically when rendering the page. The syntax of a <gradient> is:

<gradient> = [
  <linear-gradient()> | <repeating-linear-gradient()> |
  <radial-gradient()> | <repeating-radial-gradient()> |
  <conic-gradient()>  | <repeating-conic-gradient()> ]

A gradient is drawn into a box with the dimensions of the concrete object size, referred to as the gradient box. However, the gradient itself has no natural dimensions.

Gradients are specified by defining the starting point and ending point of a gradient line (which, depending on the type of gradient, may be technically a line, or a ray, or a spiral), and then specifying colors at points along this line. The colors are smoothly blended to fill in the rest of the line, and then each type of gradient defines how to use the color of the gradient line to produce the actual gradient.

3.1. Linear Gradients: the linear-gradient() notation

Compared to [css3-images], this level adds a <color-interpolation-method> token to customize color interpolation in gradients as described in CSS Color 4 § 12 Color Interpolation.

linear-gradient() = linear-gradient(
  [ <angle> | to <side-or-corner> ]? || <color-interpolation-method>,
  <color-stop-list>
)
<side-or-corner> = [left | right] || [top | bottom]

The effect of colorspace on interpolation can be marked.

Chosing a polar, rather than rectangular, colorspace for gradient interpolation avoids desaturation if the hues of the color stops are far apart. Interpolating in a polar colorspaces is inherently chroma-preserving, although it is easy for the intermediate colors to fall out of gamut; they will then be gamut mapped to bring them back into gamut.

3.2. Radial Gradients: the radial-gradient() notation

Compared to [css3-images], this level adds a <color-interpolation-method> token to customize color interpolation in gradients as described in CSS Color 4 § 12 Color Interpolation.

radial-gradient() = radial-gradient(
  [[ <ending-shape> || <size> ]? [ at <position> ]? ] || <color-interpolation-method>,
  <color-stop-list>
)

3.3. Conic Gradients: the conic-gradient() notation

A conic gradient starts by specifying the center of a circle, similar to radial gradients, except that conic gradient color-stops are placed around the circumference of the circle, rather than on a line emerging from the center, causing the color to smoothly transition as you spin around the center, rather than as you progress outward from the center.

A conic gradient is specified by indicating a rotation angle, the center of the gradient, and then specifying a list of color-stops. Unlike linear and radial gradients, whose color-stops are placed by specifying a <length>, the color-stops of a conic gradient are specified with an <angle>. Rays are then drawn emerging from the center and pointing in all directions, with the color of each ray equal to the color of the gradient-line where they intersect it.

Note: These gradients are called "conic" or "conical" because, if the color stops are chosen to be significantly lighter on one side than the other, it produces a pattern that looks like a cone observed from above. They are also known as "angle" gradients in some contexts, since they are produced by varying the rotation angle of a ray.

This example visually illustrates how conic-gradient(at 25% 30%, white, black 60%) would be drawn. Note that since color stop positions always resolve to angles, the only effect of the at 25% 30% is a 2D translation of the gradient, i.e. it does not affect how the gradient is drawn.

3.3.1. conic-gradient() Syntax

The syntax for a conic gradient is:

conic-gradient() = conic-gradient(
  [ [ from <angle> ]? [ at <position> ]? ] || <color-interpolation-method>,
  <angular-color-stop-list>
)

The arguments are defined as follows:

<angle>

The entire gradient is rotated by this angle. If omitted, defaults to 0deg. The unit identifier may be omitted if the <angle> is zero.

<position>

Determines the gradient center of the gradient. The <position> value type (which is also used for background-position) is defined in [CSS-VALUES-3], and is resolved using the center-point as the object area and the gradient box as the positioning area. If this argument is omitted, it defaults to center.

Usually in conic gradients the sharp transition at 0deg is undesirable, which is typically avoided by making sure the first and last color stops are the same color. Perhaps it would be useful to have a keyword for automatically achieving this.

Would a radius (inner & outer) for clipping the gradient be useful? If so, we could also support lengths in color stop positions, since we now have a specific radius.

Are elliptical conic gradients useful? Do graphics libraries support them?

3.3.2. Placing Color Stops

Color stops are placed on a gradient line that curves around the gradient center in a circle, with both the 0% and 100% locations at 0deg. Just like linear gradients, 0deg points to the top of the page, and increasing angles correspond to clockwise movement around the circle.

Note: It may be more helpful to think of the gradient line as forming a spiral, where only the segment from 0deg to 360deg is rendered. This avoids any confusion about "overlap" when you have angles outside of the rendered region.

A color-stop can be placed at a location before 0% or after 100%; though these regions are never directly consulted for rendering, color stops placed there can affect the color of color-stops within the rendered region through interpolation or repetition (see repeating gradients). For example, conic-gradient(red -50%, yellow 150%) produces a conic gradient that starts with a reddish-orange color at 0deg (specifically, #f50), and transitions to an orangish-yellow color at 360deg (specifically, #fa0).

The color of the gradient at any point is determined by first finding the unique ray anchored at the center of the gradient that passes through the given point. The point’s color is then the color of the gradient line at the location where this ray intersects it.

3.3.3. Conic Gradient Examples

All of the following conic-gradient() examples are presumed to be applied to a box that is 300px wide and 200px tall, unless otherwise specified.

background: conic-gradient(#f06, gold);
background: conic-gradient(at 50% 50%, #f06, gold);
background: conic-gradient(from 0deg, #f06, gold);
background: conic-gradient(from 0deg at center, #f06, gold);
background: conic-gradient(#f06 0%, gold 100%);
background: conic-gradient(#f06 0deg, gold 1turn);

background: conic-gradient(white -50%, black 150%);
background: conic-gradient(white -180deg, black 540deg);
background: conic-gradient(hsl(0,0%,75%), hsl(0,0%,25%));

background: conic-gradient(from 45deg, white, black, white);
background: conic-gradient(hsl(0,0%,75%), white 45deg, black 225deg, hsl(0,0%,75%));

background: conic-gradient(white 45deg, black 225deg, white 405deg);

background: radial-gradient(gray, transparent),
            conic-gradient(red, magenta, blue, aqua, lime, yellow, red);
border-radius: 50%;
width: 200px; height: 200px;

background: conic-gradient(yellowgreen 40%, gold 0deg 75%, #f06 0deg);
border-radius: 50%;
width: 200px; height: 200px;

3.4. Repeating Gradients: the repeating-linear-gradient(), repeating-radial-gradient(), and repeating-conic-gradient() notations

In addition to linear-gradient(), radial-gradient(), and conic-gradient(), this specification defines repeating-linear-gradient(), repeating-radial-gradient(), and repeating-conic-gradient() values. These notations take the same values and are interpreted the same as their respective non-repeating siblings defined previously.

background: repeating-conic-gradient(gold, #f06 20deg);

background: repeating-conic-gradient(
                hsla(0,0%,100%,.2) 0deg 15deg,
                hsla(0,0%,100%,0) 0deg 30deg
            ) #0ac;

background: repeating-conic-gradient(black 0deg 25%, white 0deg 50%);
background-size: 60px 60px;

background: conic-gradient(black 25%, white 0deg 50%, black 0deg 75%, white 0deg);
background-size: 60px 60px;

3.5. Defining Gradient Color

The colors in gradients are specified using color stops (a <color> and a corresponding position on the gradient line) and color transition hints (a position between two color stops representing the halfway point in the color transition) which are placed on the gradient line, defining the color at every point of the line. (Each gradient function defines the shape and length of the gradient line, along with its starting point and ending point; see above.)

3.5.1. Color Stop Lists

Color stops and transition hints are specified in a color stop list, which is a list of two or more color stops interleaved with optional transition hints:

<color-stop-list> =
  <linear-color-stop> , [ <linear-color-hint>? , <linear-color-stop> ]#
<linear-color-stop> = <color> && <color-stop-length>?
<linear-color-hint> = <length-percentage>
<color-stop-length> = <length-percentage>{1,2}

<angular-color-stop-list> =
  <angular-color-stop> , [ <angular-color-hint>? , <angular-color-stop> ]#
<angular-color-stop> = <color> && <color-stop-angle>?
<angular-color-hint> = <angle-percentage>
<color-stop-angle> = <angle-percentage>{1,2}

<color-stop> = <color-stop-length> | <color-stop-angle>

A color stop with two positions is equivalent to specifying two color stops with the same color, one for each position. Specifying two locations makes it easier to create solid-color "stripes" in a gradient, without having to repeat the color twice.

Percentages are resolved against the length of the gradient line between the starting point and ending point, with 0% being at the starting point and 100% being at the ending point. Lengths are measured along the gradient line from the starting point in the direction of the ending point.

Color stop and transition hint positions are usually placed between the starting point and ending point, but that’s not required: the gradient line extends infinitely in both directions, and positions can be specified anywhere on the gradient line.

When the position of a color stop is omitted, it is automatically assigned a position. The first or last color stop in the color stop list is assigned the gradient line’s starting point or ending point (respectively). Otherwise, it’s assigned the position halfway between the two surrounding stops. If multiple stops in a row lack a position, they space themselves out equally between the surrounding positioned stops. See § 3.5.3 Color Stop “Fixup” for details.

3.5.2. Coloring the Gradient Line

At each color stop position, the gradient line is the color of the color stop. Before the first color stop, the gradient line is the color of the first color stop, and after the last color stop, the gradient line is the color of the last color stop. Between two color stops, the gradient line’s color is interpolated between the colors of the two color stops, with the interpolation taking place in the specified color space, using premultiplied alpha, as defined in CSS Color 4 § 12.3 Interpolating with Alpha. If no <color-interpolation-method> is specified in the gradient function, the color space used for gradient interpolation is the default interpolation color space as defined in [css-color-4].

By default, this interpolation is linear—at 25%, 50%, or 75% of the distance between two color stops, the color is a 25%, 50%, or 75% blend of the colors of the two stops.

However, if a transition hint was provided between two color stops, the interpolation is non-linear, and controlled by the hint:

Note: The transition hint specifies where the “halfway color”—the 50% blend between the colors of the two surrounding color stops—should be placed. When the hint is exactly halfway between the two surrounding color stops, the above interpolation algorithm happens to produce the ordinary linear interpolation. If the hint is placed anywhere else, it produces a smooth exponential curve between the surrounding color stops, with the “halfway color” occurring exactly where the hint specifies.

background: linear-gradient(to right, red 0%, blue 100%);

background: linear-gradient(to right, red 0%, 25%, blue 100%);

If multiple color stops have the same position, they produce an infinitesimal transition from the one specified first in the list to the one specified last. In effect, the color suddenly changes at that position rather than smoothly transitioning.

3.5.3. Color Stop “Fixup”

When resolving the used positions of each color stop, the following steps must be applied in order:

1. If the first color stop does not have a position, set its position to 0%. If the last color stop does not have a position, set its position to 100%.
2. If a color stop or transition hint has a position that is less than the specified position of any color stop or transition hint before it in the list, set its position to be equal to the largest specified position of any color stop or transition hint before it.
3. If any color stop still does not have a position, then, for each run of adjacent color stops without positions, set their positions so that they are evenly spaced between the preceding and following color stops with positions.

After applying these rules, all color stops and transition hints will have a definite position and color and they will be in ascending order.

Note: It is recommended that authors exercise caution when mixing different types of units, such as px, em, or %, as this can cause a color stop to unintentionally try to move before an earlier one. For example, the rule background-image: linear-gradient(yellow 100px, blue 50%) wouldn’t trigger any fix-up while the background area is at least 200px tall. If it was 150px tall, however, the blue color stop’s position would be equivalent to 75px, which precedes the yellow color stop, and would be corrected to a position of 100px. Additionally, since the relative ordering of such color stops cannot be determined without performing layout, they will not interpolate smoothly in animations or transitions.

1. linear-gradient(red, white 20%, blue)
   =1=>
   linear-gradient(red 0%, white 20%, blue 100%)

2. linear-gradient(red 40%, white, black, blue)
   =1,3=>
   linear-gradient(red 40%, white 60%, black 80%, blue 100%)

3. linear-gradient(red -50%, white, blue)
   =1,3=>
   linear-gradient(red -50%, white 25%, blue 100%)

4. linear-gradient(red -50px, white, blue)
   =1,3=>
   linear-gradient(red -50px, white calc(-25px + 50%), blue 100%)

5. linear-gradient(red 20px, white 0px, blue 40px)
   =2=>
   linear-gradient(red 20px, white 20px, blue 40px)

6. linear-gradient(red, white -50%, black 150%, blue)
   =1,2=>
   linear-gradient(red 0%, white 0%, black 150%, blue 150%)

7. linear-gradient(red 80px, white 0px, black, blue 100px)
   =2,3=>
   linear-gradient(red 80px, white 80px, black 90px, blue 100px)

4. 1D Image Values: the stripes() notation

Per WG resolution, define the stripes() function which creates a 1D image for use in borders/outlines.

5. Sizing Images and Objects in CSS

5.1. Setting The Viewbox: the object-view-box property

The object-view-box property specifies a "view box" over an element, similar to the <svg viewBox> attribute, zooming or panning over the element’s contents.

none

The element does not have a view box.

<basic-shape-rect>

If the element does not have both a natural width and a natural height, this value has no effect, similar to none.

Otherwise, specifies a view box for the element.

First, resolve the <basic-shape-rect> against a reference box formed by the element’s natural sizes to obtain the element’s view box.

For all purposes, the element is now treated as having natural sizes equal to the view box’s width and height. If the element had a natural aspect ratio, it’s now treated as instead having the same ratio as the view box. Further adjustments to the size/position of the element’s contents, such as object-position or object-fit, are similarly performed on the view box instead.

When the element is painted, its contents are scaled and translated such that the element’s contents retain the same position and size, relative to the view box’s final size and position, that they had when the view box was determined (above).

Have not yet defined what happens if the view box is zero-area. It’s an error case, so precise behavior isn’t important; just need to see what impls want to do about it.

Note: Some replaced elements might have a built-in notion of a "view box", such as the svg element. Unless otherwise specified, this property does not interact with such notions; the built-in notion has its effect as normal, producing a replaced element with natural sizes, then this property applies on top of that.

5.2. Sizing Objects: the object-fit property

The object-fit property specifies how the contents of a replaced element should be fitted to the box established by its used height and width.

fill

The replaced content is sized to fill the element’s content box: the object’s concrete object size is the element’s used width and height.

none

The replaced content is not resized to fit inside the element’s content box: determine the object’s concrete object size using the default sizing algorithm with no specified size, and a default object size equal to the replaced element’s used width and height.

contain

The replaced content is sized to maintain its aspect ratio while fitting within the element’s content box: its concrete object size is resolved as a contain constraint against the element’s used width and height.

If the scale-down flag is used, size the content as if none or contain were specified, whichever would result in a smaller concrete object size.

Note: Both none and contain respect the content’s natural aspect ratio, so the concept of "smaller" is well-defined.

cover

The replaced content is sized to maintain its aspect ratio while filling the element’s entire content box: its concrete object size is resolved as a cover constraint against the element’s used width and height.

If the scale-down flag is used, size the content as if none or cover were specified, whichever would result in a smaller concrete object size.

Note: Both none and cover respect the content’s natural aspect ratio, so the concept of "smaller" is well-defined.

scale-down

Equivalent to contain scale-down.

If the content does not completely fill the replaced element’s content box, the unfilled space shows the replaced element’s background. Since replaced elements always clip their contents to the content box, the content will never overflow. See the object-position property for positioning the object with respect to the content box.

Note: The object-fit property has similar semantics to the fit attribute in [SMIL10] and the <meetOrSlice> parameter on the preserveAspectRatio attribute in [SVG11].

Note: Per the object size negotiation algorithm, the concrete object size (or, in this case, the size of the content) does not directly scale the object itself - it is merely passed to the object as information about the size of the visible canvas. How to then draw into that size is up to the image format. In particular, raster images always scale to the given size, while SVG uses the given size as the size of the "SVG Viewport" (a term defined by SVG) and then uses the values of several attributes on the root <svg> element to determine how to draw itself.

6. Image Processing

6.1. Overriding Image Resolutions: the image-resolution property

The image resolution is defined as the number of image pixels per unit length, e.g., pixels per inch. Some image formats can record information about the resolution of images. This information can be helpful when determining the actual size of the image in the formatting process. However, the information can also be wrong, in which case it should be ignored. By default, CSS assumes a resolution of one image pixel per CSS px unit; however, the image-resolution property allows using some other resolution.

The image-set() notation can alter the natural resolution of an image, which ideally would be automatically honored without having to set this property. How should we best address this? Change the initial value to auto, meaning "1dppx, unless CSS says otherwise"? Say that image-resolution has no effect on images whose resolution was set by something else in CSS? Or somehow wordsmithing image-set() in some way such that it always produces 1dppx images somehow?

The image-resolution property specifies the preferred resolution of all raster images used in or on the element. It affects both content images (e.g. replaced elements and generated content) and decorative images (such as background-image). The preferred resolution of an image is used to determine the image’s natural dimensions. Values have the following meanings:

<resolution>

Specifies the preferred resolution explicitly. A "dot" in this case corresponds to a single image pixel.

from-image

The image’s preferred resolution is taken as that specified by the image format (the natural resolution). If the image does not specify its own resolution, the explicitly specified resolution is used (if given), else it defaults to 1dppx.

Note: CSS Images 3 § 2.1.2 Image Metadata imposes some restrictions on what metadata can be used.

snap

If the "snap" keyword is provided, the computed <resolution> (if any) is the specified resolution rounded to the nearest value that would map one image pixel to an integer number of device pixels. If the resolution is taken from the image, then the used natural resolution is the image’s native resolution similarly adjusted.

As vector formats such as SVG do not have a natural resolution, this property has no effect on vector images.

img.high-res {
  image-resolution: 300dpi;
}

img { image-resolution: from-image }

img { image-resolution: from-image 300dpi }
img { image-resolution: 300dpi from-image }

img { image-resolution: 300dpi }

img { image-resolution: 300dpi snap; }

img { image-resolution: snap from-image; }

7. Interpolation

This section describes how to interpolate between new value types defined in this specification, for use with modules such as CSS Transitions and CSS Animations.

If an algorithm below simply states that two values should be "interpolated" or "transitioned" without further details, then the value should be interpolated as described by the Transitions spec. Otherwise, the algorithm may reference a variable t in its detailed description of the interpolation. This is a number which starts at 0% and goes to 100%, and is set to a value that represents the progress through the transition, based on the duration of the transition, the elapsed time, and the timing function in use. For example, with a linear timing function and a 1s duration, after .3s t is equal to 30%.

7.1. Interpolating <image>

All images can be interpolated, though some special types of images (like some gradients) have their own special interpolation rules. In general terms, images are interpolated by scaling them to the size of the start image and cross-fading the two while they transition to the size of the end image.

In specific terms, at each point in the interpolation the image is equal to cross-fade( (100% - t) start image, end image).

Special-case interpolating to/from no image, like "background-image: url(foo);" to "background-image: none;".

7.2. Interpolating cross-fade()

The three components of cross-fade() are interpolated independently. Note this may result in nested cross-fade() notations.

7.3. Interpolating <gradient>

This section needs review and improvement. In particular, I believe the handling of linear-gradient() is incomplete - I think we want to specifically interpolate the "length" of the gradient line (the distance between 0% and 100%) between the starting and ending positions explicitly, so it doesn’t grow and then shrink over a single animation.

Gradient images can be interpolated directly in CSS transitions and animations, smoothly animating from one gradient to another. There are only a few restrictions on what gradients are allowed to be interpolated:

1. Both the starting and ending gradient must be expressed with the same function. (For example, you can transition from a linear-gradient() to a linear-gradient(), but not from a linear-gradient() to a radial-gradient() or a repeating-linear-gradient().)

2. Both the starting and ending gradient must have the same number of <color-stop>s. For this purpose, all repeating gradients are considered to have infinite color stops, and thus all repeating gradients match in this respect.

3. Neither gradient uses a combination of <length> and <percentage> color stops.

If the two gradients satisfy all of those constraints, they must be interpolated as described below. If they fail the third one only, they must be abruptly transitioned at 50% (unless otherwise specified by a future specification). If they fail either of the first two constraints, they must be interpolated using cross-fade() as for generic images.

Note: The abrupt transition at 50% is so that content will not rely on cross-fading, and smarter interpolation rules can be added for this case in the future.

1. Convert both the start and end gradients to their explicit forms:

   For linear gradients:

   • If the direction is specified as an <angle>, it is already in its explicit form.

   • Otherwise, change its direction to an <angle> in [0deg,360deg) that would produce an equivalent rendering.

     If both the start and end gradients had their direction specified with keywords, and the absolute difference between the angles their directions mapped to is greater than 180deg, add 360deg to the direction of the gradient with the smaller angle. This ensures that a transition from, for example, "to left" (270deg) to "to top" (0deg) rotates the gradient a quarter-turn clockwise, as expected, rather than rotating three-quarters of a turn counter-clockwise.

   For radial gradients:

   • If the size is specified as two <length>s or <percentage>s, it is already in its explicit form.

   • Otherwise, the size must be changed to a pair of <length>s that would produce an equivalent ending-shape. If the <ending-shape> was specified as circle, change it to ellipse.

2. Interpolate each component and color-stop of the gradients independently. For linear gradients, the only component is the angle. For radial gradients, the components are the horizontal and vertical position of the center and the horizontal and vertical axis lengths.

3. To interpolate a color-stop, first match each color-stop in the start gradient to the corresponding color-stop at the same index in the end gradient. For repeating gradients, the first specified color-stop in the start and end gradients are considered to be at the same index, and all other color-stops following and preceding are indexed appropriately, repeating and shifting each gradient’s list of color-stops as needed. Then, for each pair of color-stops, interpolate the position and color independently.

8. Serialization

This section describes the serialization of all new properties and value types introduced in this specification, for the purpose of interfacing with the CSS Object Model [CSSOM].

To serialize any function defined in this module, serialize it per its individual grammar, in the order its grammar is written in, omitting components when possible without changing the meaning, joining space-separated tokens with a single space, and following each serialized comma with a single space.

For cross-fade(), always serialize the <percentage>.

Linear-Gradient( to bottom, red 0%,yellow,black 100px)

linear-gradient(rgb(255, 0, 0), rgb(255, 255, 0), rgb(0, 0, 0) 100px)

Appendix A: Deprecated Features and Aliases

Implementations must accept -webkit-image-set() as a parse-time alias of image-set(). (It’s a valid value, with identical arguments to image-set(), and is turned into image-set() during parsing.)

9. Privacy Considerations

Note: No change from [css3-images].

10. Security Considerations

Note: No change from [css3-images].

11. Changes

Changes Since the 13 April 2017 Working Draft

• Added an example of a color hint

• Fixed typos in examples

• Defined fetching of external images

• Added <color-interpolation-method> to all gradient functions

• Added the -webkit-image-set() alias

• Clarified the image-resolution property

• Added type() to image-set()

• Added <element()> to <image> data type

• Defined image replacement case of loading images

• Copied definition of computed <image> from [css3-images]

• Backported the editorial changes about color stops from [css3-images]

• Properly specified behavior of image() when it contains only a URL, and that URL is invalid/loading.

• copied definition of loading image from [css3-images]

• Rewrote the color-stops section for better clarity

• Added intro text and note talking about color stop lists

• Switched color-stop grammar to repeat at end for readability

• Clarified that object-fit and image-resolution use discrete animation

• Fixed definition of cross-fade() image blending

• Added placeholder section for the stripes() function

• Moved interpolation of images from [css3-images]

• Clarifed that cross-fade() takes 1+ arguments. Defined sizing and painting of the new function arguments in detail.

• Moved cross-fade() from [css3-images]

• Dropped "Media:" entry from propdef tables

• Changed IDL partial interface to a namespace

• Clarified unitless zero

• Made scale-down a flag for cover/contain

• Renamed module, shorter name

• Moved image-set() from [css3-images]

• Added new examples, corrected incorrect examples

• Assorted markup fixes, corrections to property syntaxes, inline issues, spelling corrections, and minor editorial refinements

Changes Since the 11 September 2012 Working Draft

• Added color interpolation hints

• Added the two location syntax for gradient color stops

• Added start angles to conic gradients

• The position(s) of a color stop can now come before the color

• Text that is identical to [css3-images] has been replaced with a reference to [css3-images].

• Added the -webkit-image-set() alias.

Changes Since Level 3

• Added the image() notation (deferred from Level 3)

• Added the image-resolution property (deferred from Level 3)

• Added the element() notation (deferred from Level 3)

• Added conic gradients

• Added <color-interpolation-method> to all gradient functions