Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/TR/css-align/ below:

CSS Box Alignment Module Level 3

CSS Levels 1 and 2 allowed for the alignment of text via text-align and the alignment of blocks by balancing auto margins. However, except in table cells, vertical alignment was not possible. As CSS adds further capabilities, the ability to align boxes in various dimensions becomes more critical. This module attempts to create a cohesive and common box alignment model to share among all of CSS.

Note: The alignment of text and inline-level content is defined in [CSS-TEXT-3] and [CSS-INLINE-3].

Note: This specification is not intended to change any of the behavior defined in CSS2.1 when the properties defined here are set to their initial values. If implementors or anyone else notices a discrepancy, please report this to the CSSWG as an error.

This section (above) is not normative.

This module adds some new alignment capabilities to the block layout model described in [CSS2] chapters 9 and 10, redefines how overconstrained block-level box margins are resolved, and defines the interaction of these new alignment properties with the alignment of table cell content using vertical-align, as defined in [CSS2] chapter 17.

The interaction of these properties with Grid Layout [CSS-GRID-1] and Flexible Box Layout [CSS-FLEXBOX-1] is defined in their respective modules. The property definitions here supersede those in [CSS-FLEXBOX-1] (which have a smaller, earlier subset of permissible values).

No properties in this module apply to the ::first-line or ::first-letter pseudo-elements.

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.

Since it is expected that support for the features in this module will be deployed in stages corresponding to the various layout models affected, it is hereby clarified that the rules for partial implementations that require treating as invalid any unsupported feature apply to any alignment keyword which is not supported across all layout modules to which it applies for layout models in which the implementation supports the property in general.

For example, if an implementation supports align-self in [CSS-GRID-1] and [CSS-FLEXBOX-1], then it must treat start as invalid unless it is supported in both grid and flex containers. However if that same implementation does not support align-self for block-level elements at all, then a lack of implementation of align-self: start does not trigger this requirement to treat it as invalid.

The box alignment properties in CSS are a set of 6 properties that control alignment of boxes within other boxes. They can be described along two axises:

• which dimension they apply to (main/inline vs. cross/block), and
• whether they control the position of the box within its parent, or the box’s content within itself.

Note: This specification uses the terms “justify” and “align” to distinguish between alignment in the main/inline and cross/block dimensions, respectively. The choice is somewhat arbitrary, but having the two terms allows for a consistent naming scheme that works across all of CSS’s layout models (including CSS Flexbox 1 § 2 Flex Layout Box Model and Terminology)

The following table summarizes the box alignment properties and the display types they can apply to.

Note: The *-items properties don’t affect the element itself. When set on a container, they specify the interpretation of any *-self: auto used on children of the container element.

Since this module defines alignment properties for all layout modes in CSS, some abstract terminology is introduced:

alignment subject

The alignment subject is the thing or things being aligned by the property. For justify-self and align-self, the alignment subject is the margin box of the box the property is set on, and assumes the writing mode of that box. For justify-content and align-content, the alignment subject is defined by the layout mode and refers to some aspect of its contents; it also assumes the writing mode of the box the property is set on.

alignment container

The alignment container is the rectangle that the alignment subject is aligned within. This is defined by the layout mode, but is usually the alignment subject’s containing block, and assumes the writing mode of the box establishing the containing block.

fallback alignment

Some alignments can only be fulfilled in certain situations or are limited in how much space they can consume; for example, space-between can only operate when there is more than one alignment subject, and baseline alignment, once fulfilled, might not be enough to absorb all the excess space. In these cases a fallback alignment takes effect (as defined below) to fully consume the excess space.

All of the alignment properties use a common set of keyword values, which are defined in this section. Keywords fall into three categories:

positional alignment

These keywords define alignment as an absolute position within the alignment container.

baseline alignment

These keywords define alignment as a relationship among the baselines of multiple alignment subjects within an .

distributed alignment

These keywords define alignment as a distribution of space among alignment subjects.

The positional alignment keywords specify a position for an alignment subject with respect to its alignment container.

Values have the following meanings:

center (self, content)

Centers the alignment subject within its alignment container.

start (self, content)

Aligns the alignment subject to be flush with the alignment container’s start edge in the appropriate axis.

end (self, content)

Aligns the alignment subject to be flush with the alignment container’s end edge in the appropriate axis.

self-start (self)

Aligns the alignment subject to be flush with the edge of the alignment container corresponding to the alignment subject’s start side in the appropriate axis.

self-end (self)

Aligns the alignment subject to be flush with the edge of the alignment container corresponding to the alignment subject’s end side in the appropriate axis.

flex-start (self, content)

Only used in flex layout. [CSS-FLEXBOX-1] Aligns the alignment subject to be flush with the edge of the alignment container corresponding to the flex container’s main-start or cross-start side, as appropriate.

When used outside of a flex formatting context, this value behaves as start. That is, on boxes that are not flex items (or pretending to be flex items, such as when determining the static position of an absolutely-positioned box that is a child of a flex container), this value behaves as start when used in the self-alignment properties, and on boxes that are not flex containers, this value behaves as start when used in the content-distribution properties.

flex-end (self, content)

Only used in flex layout. Aligns the alignment subject to be flush with the edge of the alignment container corresponding to the flex container’s main-end or cross-end side, as appropriate.

When used outside of a flex formatting context, this value behaves as end. That is, on boxes that are not flex items (or pretending to be flex items, such as when determining the static position of an absolutely-positioned box that is a child of a flex container), this value behaves as end when used in the self-alignment properties, and on boxes that are not flex containers, this value behaves as end when used in the content-distribution properties.

left (only justify-*)

Aligns the alignment subject to be flush with the alignment container’s line-left or physical left edge, whichever is in the appropriate axis.

If the property’s axis is not parallel with either left↔right axis, this value behaves as start. Currently, the only case where the property’s axis is not parallel with either left↔right axis is in a column flexbox.

right (only justify-*)

Aligns the alignment subject to be flush with the alignment container’s line-right or physical right edge, whichever is in the appropriate axis.

If the property’s axis is not parallel with either left↔right axis, this value behaves as start. Currently, the only case where the property’s axis is not parallel with either left↔right axis is in a column flexbox.

Two grammar terms are used to denote certain subsets of these values:

<self-position>

This set is used by justify-self and align-self to align the box within its alignment container, and also by justify-items and align-items (to specify default values for justify-self and align-self).

<self-position> = center | start | end | self-start | self-end |
        flex-start | flex-end

<content-position>

This set is used by justify-content and align-content to align the box’s contents within itself.

<content-position> = center | start | end | flex-start | flex-end

Note: left and right are excluded from <self-position> and <content-position>, despite being valid positional alignment values for justify-content/justify-self/justify-items, because they are not allowed in the align-* properties. They are instead explicitly included in the justify-* properties’ grammars.

The left and right keywords are absolute (not flow-relative).

The start and end keywords have meaning in both the inline and block axes: start always orients to the start of the text (top left for left-to-right/top-to-bottom languages like English) while end always orients to the end of the text.

The start and end keywords use the writing mode of the alignment container, to help keep things consistent. But if alignment using the alignment subject’s writing mode is needed, the self-start and self-end keywords can be used.

For most layout models (block, table, grid, etc), the

properties always align things in the

, while the

properties always align things in the

.

Flexbox, on the other hand, has justify-* align things in the main axis and align-* align things in the cross axis. This depends on the value of flex-direction: when flex-direction is row or row-reverse, it matches the other layout modes (inline axis with justify-*, block axis with align-*); when flex-direction is column or column-reverse, it has the opposite correspondence.

Make it easier to understand the dual-axis nature of "start" and "end" wrt orthogonal flows.

See CSS Writing Modes 3 § 4.1 Introduction to Baselines.

Baseline alignment is a form of positional alignment that aligns multiple alignment subjects within a (such as cells within a row) by matching up their alignment baselines. If the position of the alignment subjects within a baseline-sharing group is not fully constrained by baseline alignment (i.e., they could be shifted within their respective alignment containers while maintaining baseline-alignment), they are fallback-aligned insofar as possible while preserving their baseline alignment.

The baseline alignment keywords are represented with the <baseline-position> grammar term:

<baseline-position> = [ first | last ]? && baseline

The first and last values give a box a baseline alignment preference: either “first” or “last”, respectively, defaulting to “first”.

Values have the following meanings:

baseline

Computes to first baseline, defined below.

first baseline

Specifies participation in first-baseline alignment: aligns the alignment baseline of the box’s first baseline set with the corresponding baseline of its baseline-sharing group. See § 9.3 Aligning Boxes by Baseline for more details.

The fallback alignment for first baseline is safe self-start (for self-alignment) or safe start (for content-distribution).

last baseline

Specifies participation in last-baseline alignment: aligns the alignment baseline of the box’s last baseline set with the corresponding baseline of its baseline-sharing group.̣ See § 9.3 Aligning Boxes by Baseline for more details.

The fallback alignment for last baseline is safe self-end (for self-alignment) or safe end (for content-distribution).

When specified for align-content, these values trigger baseline content-alignment, shifting the content of the box within its content box, and may also affect the sizing of the box itself. See § 5.4 Baseline Content-Alignment.

When specified for align-self/justify-self, these values trigger baseline self-alignment, shifting the entire box within its container, which may affect the sizing of its container. See § 6.4 Baseline Self-Alignment.

When baseline self-alignment is specified on a box, content distribution is performed first, then the resulting box and its contents are self-aligned However, if the box also has baseline content-alignment in the same axis or if its content-distribution property in the same axis is normal, its used content-distribution property in that axis is start or safe end for a baseline alignment preference of its baseline self-alignment of “first” or “last”, respectively.

Add example images here.

If a box does not belong to a , then the fallback alignment is used. For example, align-content: baseline on a block box falls back to start alignment. The fallback alignment is also used to align the baseline-sharing group within its alignment container.

Note: Because they are equivalent, and baseline is shorter, the CSSOM serializes first baseline as baseline. See CSSOM § 6.7.2 Serializing CSS Values.

Note: For the somewhat-related vertical-align property, due to inconsistent design decisions in CSS2.1, baseline is not equivalent to first baseline as an inline-level box’s baseline alignment preference depends on display. (E.g., inline-block uses its last baseline by default, while inline-table uses its first baseline by default.)

The distributed alignment values are used by justify-content and align-content to disperse a container’s extra space among its alignment subjects.

When space cannot be distributed in this way, these values behave as their fallback alignment. Each distribution value has an associated default fallback alignment. (A future level of this module may allow the fallback alignment to be specified explicitly.)

space-between

The alignment subjects are evenly distributed in the alignment container. The first alignment subject is placed flush with the start edge of the alignment container, the last alignment subject is placed flush with the end edge of the alignment container, and the remaining alignment subjects are distributed so that the spacing between any two adjacent alignment subjects is the same.

The default fallback alignment for this value is safe flex-start. (For layout modes other than flex layout, flex-start is identical to start.)

space-around

The alignment subjects are evenly distributed in the alignment container, with a half-size space on either end. The alignment subjects are distributed so that the spacing between any two adjacent alignment subjects is the same, and the spacing before the first and after the last alignment subject is half the size of the other spacing.

The default fallback alignment for this value is safe center.

space-evenly

The alignment subjects are evenly distributed in the alignment container, with a full-size space on either end. The alignment subjects are distributed so that the spacing between any two adjacent alignment subjects, before the first alignment subject, and after the last alignment subject is the same.

The default fallback alignment for this value is safe center.

stretch

If the combined size of the alignment subjects is less than the size of the alignment container, any auto-sized alignment subjects have their size increased equally (not proportionally), while still respecting the constraints imposed by max-height/max-width (or equivalent functionality), so that the combined size exactly fills the alignment container.

The default fallback alignment for this value is flex-start. (For layout modes other than flex layout, flex-start is identical to start.)

Note: This `align-content/stretch` definition applies to the content-distribution properties; the self-alignment properties justify-self/align-self have their own stretch value, which can grow or shrink the alignment subject to ensure it exactly fits the alignment container.

These values are represented with the <content-distribution> grammar term:

<content-distribution> = space-between | space-around | space-evenly | stretch

When the alignment subject is larger than the alignment container, it will overflow. Some alignment modes, if honored in this situation, may cause data loss: for example, if the contents of a sidebar are centered, when they overflow they may send part of their boxes past the viewport’s start edge, which can’t be scrolled to.

The figure below illustrates the difference in “safe” versus “unsafe” centering, using a column flexbox as an example:

About

Authoritarianism

Blog

About

Authoritarianism

Blog

The items in the figure on the left are centered unless they overflow, in which case all the overflow goes off the end edge, while those in the figure on the right are are all strictly centered, even if the one that is too long to fit overflows on both sides.

If the container was placed against the left edge of the page, the “safe” behavior would be more desirable, as the long item would be fully readable, rather than clipped by the left edge of the screen. In other circumstances, the “unsafe” centering behavior might be better, as it correctly centers all the items.

To control this situation, an overflow alignment mode can be explicitly specified. “Unsafe” alignment honors the specified alignment mode in overflow situations, even if it causes data loss, while “safe” alignment changes the alignment mode in overflow situations in an attempt to avoid data loss. The default behavior is to contain the alignment subject within the scrollable area, though at the time of writing this safety feature is not yet implemented.

<overflow-position> = unsafe | safe

safe

If the size of the alignment subject overflows the alignment container, the alignment subject is instead aligned as if the alignment mode were start.

unsafe

Regardless of the relative sizes of the alignment subject and alignment container, the given alignment value is honored.

(no value specified)

If the overflow alignment isn’t explicitly specified, the default overflow alignment is a blend of “safe” and “unsafe”. See § 4.4.1 Automatic Overflow Alignment Safety for details.

If no overflow alignment mode is specified for a property, the default behavior lies somewhere between safe and unsafe, and also varies by layout mode.

The default overflow alignment behavior for content distribution on scroll containers is unsafe. Non-normal values of the content-distribution properties instead alter the scrollable overflow area in order to allow access to the overflowing content. See § 5.3 Alignment Overflow and Scroll Containers.

For absolutely positioned alignment subjects whose relevant self-alignment property is not normal, the default overflow alignment behavior is as follows:

(For absolutely-positioned alignment subjects that fail the above condition, see § 4.4.1.3 All Other Alignment.)

For all other elements:

1. If the alignment subject overflows its alignment container, align as specified (unsafe).

2. If the alignment subject would overflow the scrollable overflow area of its nearest ancestor scroll container, (thus extending into the “unscrollable” region), then its overflow in that direction is limited by biasing any remaining overflow to the opposite side.

It may not be Web-compatible to implement the “smart” default behavior (though we hope so, and believe it to be likely), so UAs should pass any feedback on this point to the WG. UAs that have not implemented the “smart” default behavior must behave as safe for align-content on block containers and unsafe otherwise.

Content distribution controls alignment of the box’s content within its content box. It is specified by the content-distribution properties align-content and justify-content (and their place-content shorthand).

Aligns the contents of the box as a whole (as the alignment subject) within the box itself (as the alignment container): along the inline/row/main axis of the box (for justify-content) or the block/column/cross axis of the box (for align-content). Values other than normal are defined in § 4 Alignment Keywords, above.

For all layout modes, the alignment subject and alignment container both assume the writing mode of the box the *-content property is set on.

See [CSS-FLEXBOX-1] for details.

See [CSS-GRID-1] for details.

This shorthand property sets both the align-content and justify-content properties in one declaration. The first value is assigned to align-content. The second value is assigned to justify-content; if omitted, it is copied from the first value, unless that value is a <baseline-position> in which case it is defaulted to start.

When the content-distribution properties are set on a scroll container with an overflowing alignment subject, they reduce the clipping of the negative scrollable overflow region just enough to ensure that alignment subject can be scrolled into its start-aligned position.

For example, if a scrollable flex container is set to

(or

with

), its

content will be initially positioned to align the main-end edge of its content to the main-end edge of the flex container, and its content will appear to overflow its main-start edge. However, the viewer will be able to scroll

to view the overflowing

content, just as if

had been specified.

Note: The alignment subject is not necessarily identical to the scrollable overflow area: content overflowing the alignment subject—​such as an out-of-flow box—​grows the scrollable overflow area but not the alignment subject. Thus an end-aligned scroll container might not be initially scrolled all the way to the bottom, and positioned content can still be clipped if it is further into the negative scrollable overflow region than the in-flow content forming the alignment subject.

Replace this image too.

Note: The presence of scrollbars can change the size of the scroll container’s content box—​and thus the size of the alignment container and/or alignment subject.

The content of boxes participating in row-like layout contexts () can be baseline-aligned to each other. Baseline content-alignment effectively increases the padding on the box to align the alignment baseline of its contents with that of other baseline-aligned boxes in its baseline-sharing group.

Baseline content-alignment can only apply if the align-content axis is parallel with the box’s block axis (i.e. it does not apply to “column” flex containers); otherwise the fallback alignment is used.

The set of boxes that participate in baseline content-alignment depends on the layout model:

Table Cells:

A (non-replaced) table cell participates in first/last baseline content-alignment in its startmost/endmost row if its inline axis is parallel to that of the table itself and its computed align-content is first baseline (last baseline).

Note: Baseline content-alignment of cells sharing a column is not supported; however this may be added in a future level if there is sufficient demand and implementer interest.

Flex Items:

A non-replaced flex item participates in first/last baseline content-alignment in its flex line if its computed align-content is first baseline/last baseline and its inline axis is parallel to the main axis.

Grid Items:

A non-replaced grid item participates in first/last baseline content-alignment in its startmost/endmost row or column (whichever is parallel to its inline axis) and if its computed align-content is first baseline/last baseline.

Additionally, in order to participate in baseline content-alignment it must also have a coordinated self-alignment preference, to guarantee that the box lines up the relevant edge with other boxes in its baseline-sharing group. That is, the box’s start (end) margin edge must be intended to align—​and actually align—​to the corresponding edge of its containing block when its baseline alignment preference is “first” (“last”). It otherwise takes its fallback alignment.

A box’s start margin edge is aligned to the corresponding edge of its containing block and it has a coordinated self-alignment preference for a “first” baseline alignment preference when, in the relevant axis:

• There are no auto margins and the relevant self-alignment property either is or aligns identically to stretch or self-start; or

• There is only an auto end-edge margin, which absorbs any positive free space and disables the effects of any self-alignment property, and its margin box does not overflow its containing block under circumstances that would cause it to effectively end-align instead (such as having a containing block with an opposite writing mode).

A box’s end margin edge is aligned to the corresponding edge of its containing block and it has a coordinated self-alignment preference for a “last” baseline alignment preference when, in the relevant axis:

• There are no auto margins and the relevant self-alignment property either is or aligns identically to self-end and its self-alignment is what would result from an unsafe overflow alignment; or

• There is only an auto start-edge margin, which absorbs any positive free space and disables the effects of any self-alignment property and its margin box does not overflow its containing block under circumstances that would cause it to effectively start-align instead.

See § 9.3 Aligning Boxes by Baseline for additional details. Baseline content-alignment can increase the intrinsic size of the box.

Self-alignment controls alignment of the box within its containing block. It is specified by the self-alignment properties align-self and justify-self (and their place-self shorthand).

Justifies the box (as the alignment subject) within its containing block (as the alignment container) along the inline/row/main axis of the alignment container: the box’s outer edges are aligned within its alignment container as described by its alignment value. Values have the following meanings:

auto

Behaves as normal if the box has no parent, or when determining the actual position of an absolutely positioned box. It behaves as the computed justify-items value of the parent box (minus any legacy keywords) otherwise (including when determining the static position of an absolutely positioned box).

normal

Represents the “default” alignment for the layout mode. Its behavior depends on the layout mode, as described below.

stretch

When the box’s computed width/height (as appropriate to the axis) is auto and neither of its margins (in the appropriate axis) are auto, sets the box’s used size to the length necessary to make its outer size as close to filling the alignment container as possible while still respecting the constraints imposed by min-height/min-width/max-height/max-width.

Unless otherwise specified, this value falls back to flex-start generally, and to self-start or self-end if the box has also specified first baseline or last baseline baseline content-alignment (respectively) in the same axis.

Note: The stretch keyword can cause elements to shrink, to fit their container.

<baseline-position>

Indicates baseline self-alignment, as defined in § 4.2 Baseline Alignment: the baseline keyword and first/last modifiers, § 6.4 Baseline Self-Alignment, and § 9 Baseline Alignment Details.

<overflow-position>? <self-position>

Defined in § 4 Alignment Keywords, above.

Values other than stretch cause a width/height of auto to be treated as fit-content.

Note: auto margins, because they effectively adjust the size of the margin area, take precedence over justify-self.

The effect of these rules is that an auto-sized block-level table, for example, can be aligned while still having side margins. If the table’s max-content size is narrower than its containing block, then it is shrink-wrapped to that size and aligned as specified. If the table’s max-content size is wider, then it fills its containing block, and the margins provide appropriate spacing from the containing block edges.

This section describes the effect of justify-self on how the margin box of an absolutely-positioned box is positioned with respect to its (absolute-positioning) containing block.

Values other than stretch or normal cause non-replaced absolutely-positioned boxes to use fit-content sizing for calculating auto sizes in the affected axis.

Note that stretch does cause replaced absolutely-positioned boxes to fill their containing block just as non-replaced ones do.

Note: If only one inset property is auto, the computations in CSS2 section 10.3.7 fully determine its size and position, and justify-self has no effect. (If both are auto, then the box is statically-positioned, see above, and can be aligned within the static-position rectangle.)

This property does not apply to table cells, because their position and size is fully constrained by table layout.

This property does not apply to flex items, because there is more than one item in the main axis. See flex for stretching and justify-content for main-axis alignment. [CSS-FLEXBOX-1]

See [CSS-GRID-1] for details.

Aligns the box (as the alignment subject) within its containing block (as the alignment container) along the block/column/cross axis of the alignment container: the box’s outer edges are aligned within its alignment container as described by its alignment value. Values have the following meanings:

auto

Behaves as normal if the box has no parent, or when determining the actual position of an absolutely positioned box. It behaves as the computed align-items value of the parent box (minus any legacy keywords) otherwise (including when determining the static position of an absolutely positioned box).

normal

Represents the “default” alignment for the layout mode, as defined below.

stretch

As defined for justify-self in § 6.1 Inline-Axis (or Main-Axis) Self-Alignment: the justify-self property.

<baseline-position>

Indicates baseline self-alignment, as defined in § 4.2 Baseline Alignment: the baseline keyword and first/last modifiers, § 6.4 Baseline Self-Alignment, and § 9 Baseline Alignment Details.

<overflow-position>? <self-position>

Defined in § 4 Alignment Keywords, above.

Note: auto margins, because they effectively adjust the size of the margin area, take precedence over align-self.

The align-self property does not apply to block-level boxes (including floats), because there is more than one item in the block axis.

This section describes the effect of align-self on how the margin box of an absolutely-positioned box is positioned with respect to its (absolute-positioning) containing block.

Values other than stretch or normal cause non-replaced absolutely-positioned boxes to use fit-content sizing for calculating auto sizes in the affected axis.

Note that stretch does cause replaced absolutely-positioned boxes to fill their containing block just as non-replaced ones do.

Note: If only one inset property is auto, the computations in CSS2 section 10.6.4 fully determine its size and position, and align-self has no effect. (If both are auto, then the box is statically-positioned, see above, and can be aligned within the static-position rectangle.)

This property does not apply to table cells, because their position and size is fully constrained by table layout.

See [CSS-FLEXBOX-1] for details.

See [CSS-GRID-1] for details.

This shorthand property sets both the align-self and justify-self properties in a single declaration. The first value is assigned to align-self. The second value is assigned to justify-self; if omitted, it is copied from the first value.

Boxes participating in row-like layout contexts () can be baseline-aligned to each other. Baseline self-alignment effectively increases the margins on the box to align its alignment baseline with that of other baseline-aligned boxes in its baseline-sharing group.

The set of boxes that participate in baseline self-alignment depends on the layout model:

Flex Items:

A flex item participates in first/last baseline self-alignment in its flex line if its computed align-self is first baseline/last baseline. See [CSS-FLEXBOX-1] for details.

Grid Items:

A grid item participates in first/last baseline self-alignment in its startmost/endmost row or column if its align-self or justify-self property (respectively) computes to first baseline/last baseline.

See § 9.3 Aligning Boxes by Baseline for exact details. Baseline self-alignment can increase the intrinsic size contribution of the box.

For absolutely-positioned boxes whose inline-axis offsets are both auto, the available space for calculating the inline size is also affected by alignment.

Note: In [CSS2], the available space is keyed off of the direction property of the static-position containing block. (See CSS2§10.3.7 and CSS2§10.3.8.) Fundamentally these rules set one of the auto insets (by default, the start-edge inset) to the corresponding edge of the static-position rectangle and the other to the corresponding edge of the containing block (i.e. set the inset to zero). Just as the self-alignment properties replace the containing block’s direction lookup for placement, they also replace this lookup for sizing, as specified here.

Thus, when interpreting the rules in CSS2§10.3.7 and CSS2§10.3.8, wherever the direction property of the static-position containing block is referenced, instead reference the value of the align-self or justify-self property (whichever is defined to apply to the relevant axis), treating left-equivalent alignment as defined for ltr and right-equivalent alignment as defined for rtl. Treat normal as start and any distributed alignment value as its fallback alignment.

In the case of center alignment, the available space for the box is double the distance between the center of the static-position rectangle and the closest edge of the containing block in the relevant axis.

Note: The align-self/justify-self properties can also modify additional aspects of sizing: for example, justify-self: stretch will replace “shrink-to-fit” (fit-content) sizing into the available space with stretch-fit sizing (consuming all of the available space). This is an independent effect from the available space adjustment here.

Note: This only affect how available space is calculated for sizing the absolutely-positioned box; its alignment is as specified in previous sections.

The align-items and justify-items properties (and their place-items shorthand) set the default align-self and justify-self behavior of the element’s child boxes.

This property specifies the default justify-self for all of the child boxes (including anonymous boxes) participating in this box’s formatting context. Values have the following meanings:

legacy

This keyword causes the value to effectively inherit into descendants.

If the legacy keyword appears on its own (without an accompanying left, right, or center keyword): if the inherited value of justify-items includes the legacy keyword, this value computes to the inherited value; otherwise it computes to normal.

When justify-self:auto references the value of justify-items, only the alignment keyword, not the legacy keyword, is referenced by it. It exists to implement the legacy alignment behavior of HTML’s <center> element and align attribute.

Other values have no special handling and are merely referenced by justify-self.

This property specifies the default align-self for all of the child boxes (including anonymous boxes) participating in this box’s formatting context.

Values have no special handling and are merely referenced by align-self.

This shorthand property sets both the align-items and justify-items properties in a single declaration. The first value is assigned to align-items. The second value is assigned to justify-items; if omitted, it is copied from the first value.

While margin and padding can be used to specify visual spacing around individual boxes, it’s sometimes more convenient to globally specify spacing between adjacent boxes within a given layout context, particularly when the spacing is different between sibling boxes as opposed to between the first/last box and the container’s edge.

The gap property, and its row-gap and column-gap sub-properties, provide this functionality for multi-column, flex, and grid layout.

These properties specify fixed-length gutters between items in the container, adding space between them—​in a manner similar to the space-between keyword of the content-distribution properties, but of a fixed size instead of as a fraction of remaining space. The column-gap property specifies spacing between “columns”, separating boxes in the container’s inline axis similar to inline-axis margin; while row-gap indicates spacing between “rows”, separating boxes in the container’s block axis.

Values have the following meanings:

<length-percentage [0,∞]>

Specifies a gap between “rows” or “columns”, as defined by the layout modes to which it applies; see subsections below for details.

Negative values are invalid. For percentages, see § 8.3 Percentages In gap Properties.

normal

The normal represents a used value of 1em on multi-column containers, and a used value of 0px in all other contexts.

Gutters effect a minimum spacing between items: additional spacing may be added by justify-content/align-content. Such additional space effectively increases the size of these gutters.

The exact handling of these properties varies by layout container:

multi-column containers

column-gap specifies the gutter between adjacent column boxes, see [CSS-MULTICOL-1]. row-gap specifies the gutter between the rows of column boxes established by column-height, see [CSS-MULTICOL-2].

flex containers

When applied to the main axis (e.g. column-gap in a row flex container), indicates minimum spacing between items (as if an additional fixed-size margin were inserted between adjacent flex items in a single line).

When applied to the cross axis (e.g. row-gap in a row flex container), indicates minimum spacing between adjacent flex lines.

grid containers

The row-gap and column-gap properties, when specified on a grid container, define the gutters between grid rows and grid columns, respectively. See CSS Grid Layout 1 § 10.1 Gutters: the row-gap, column-gap, and gap properties for precise details.

In all cases, the gutter disappears when it coincides with a fragmentation break. [CSS-BREAK-3]

Note: Table boxes do not use the gap properties to specify separation between their cells. Instead, they use the border-spacing property, which has slightly different functionality: it inherits, and it also specifies the additional spacing between the outermost cells and the border of the table (similar to space-evenly rather than space-between).

This property is a shorthand that sets row-gap and column-gap in one declaration. If <'column-gap'> is omitted, it’s set to the same value as <'row-gap'>.

Note: The gap property is only one component of the visible “gutter” or “alley” created between boxes. Margins, padding, or the use of distributed alignment may increase the visible separation between boxes beyond what is specified in gap.

In general, gaps introduced by the gap properties are intended to act like an empty item/track/etc with the gap’s size; in other words, an author should be able to reproduce the effects of gap by just inserting additional empty items/tracks/etc into the container.

gap always resolves percentages against the corresponding size of the content box of the element. When this size is definite, the behavior is well-defined and consistent across layout modes. But since different layout modes treat cyclic percentage sizes for items/tracks/etc differently, gap does as well:

In Grid Layout

As in the min size properties and margins/paddings [CSS-SIZING-3], cyclic percentage sizes resolve against zero for determining intrinsic size contributions, but resolve against the box’s content box when laying out the box’s contents.

In Flex Layout

Cyclic percentage sizes resolve against zero in all cases.

The Grid Layout module was originally written with its own set of gutter properties, before all such properties were unified into the existing row-gap/column-gap naming. For compatibility with legacy content, these grid-prefixed names must be supported as follows:

• grid-row-gap as a legacy name alias of the row-gap property

• grid-column-gap as a legacy name alias of the column-gap property

• grid-gap as a legacy name alias of the gap property

Boxes in a baseline-sharing group are aligned to each other using their alignment baselines. For example, in horizontal writing modes, specifying align-content: baseline on table cells in the same row will align the baselines of their first formatted lines. This section defines exactly how baseline alignment is performed in consideration of the myriad baselines and writing modes that exist in internationalized modern CSS.

A baseline set is a set of baselines (alphabetic, central, etc.) associated with a common baseline table. Typically, a typesetting tradition will use only one of these, but different writing systems use different baselines, and mixing writing systems can result in using more than one within a single line. Refer to CSS Writing Modes 3 § 4.1 Introduction to Baselines for more information on baselines and writing modes.

Each box, for a given axis, has potentially a first baseline set (and last baseline set) that nominally corresponds to the baseline set of the first/last line of text within the box. The alignment baseline, which is the baseline used to align the box in its , is one of the baselines in its baseline set, usually the dominant baseline associated with the . (See the dominant-baseline and alignment-baseline properties in [CSS-INLINE-3].)

The first and last baseline sets of a box are determined differently based on the layout model, as follows:

line box

The first/last baseline set of a line box is generated from the dominant baseline and the font settings of its root inline box.

block containers

The first/last baseline set of a block container is taken from the first/last in-flow line box in the block container or the first/last in-flow block-level child in the block container that contributes a set of first/last baselines, whichever comes first/last. If there is no such line box or child, then the block container has no baseline set.

However, for legacy reasons if its baseline-source is auto (the initial value) a block-level or inline-level block container that is a scroll container always has a last baseline set, whose baselines all correspond to its block-end margin edge.

multi-column containers

The first baseline set of a multi-column container is the first baseline set of the column or multi-column spanner with the highest (block-start–most) baseline corresponding to the multi-column container’s alignment baseline. If there is no such line box or child, then the multi-column container has no first baseline set.

The last baseline set is analogous, but uses the last baseline set and lowest (block-end–most) baseline.

tables

The first/last baseline set of a table box is the first/last baseline set of its first/last row.

When finding the first/last baseline set of an inline-block, any baselines contributed by table boxes must be skipped. (This quirk is a legacy behavior from [CSS2].)

table rows

If any cells in the row participate in first baseline/last baseline alignment along the inline axis, the first/last baseline set of the row is generated from their shared alignment baseline and the row’s first available font, after alignment has been performed. Otherwise, the first/last baseline set of the row is synthesized from the lowest and highest content edges of the cells in the row. [CSS2]

Spanning cells participate only in the first/last row that they span for the purpose of first baseline/last baseline.

flex containers

See Flex Baselines in [CSS-FLEXBOX-1].

grid containers

See Grid Baselines in [CSS-GRID-1].

To generate baselines for a box from a single baseline, use the baseline table from the font settings and first available font of that box, and align that baseline set to the given single baseline.

If a box that participates in baseline alignment has no baseline set, then its alignment baseline is synthesized according to the rules of the formatting context in which it participates. To synthesize baselines from a rectangle (or two parallel lines), synthesize the alphabetic baseline from the line-under line, and the central baseline by averaging the positions of the two edges or lines. See CSS Inline Layout 3 § A Synthesizing Alignment Metrics for rules on synthesizing additional baselines.

Note: The edges used to synthesize baselines from a box depend on their formatting context: inline-level boxes synthesize from their margin edges [CSS-INLINE-3], table cells synthesize from their content edges [CSS2], and grid and flex items synthesize from their border edges [CSS-GRID-1] [CSS-FLEXBOX-1].

In general, the writing mode of the box, shape, or other object being aligned is used to determine the line-under and line-over edges for synthesis. However, when that writing mode’s block flow direction is parallel to the axis of the , an axis-compatible writing mode must be assumed:

• If the box establishing the has a block flow direction that is orthogonal to the axis of the , use its writing mode.

• Otherwise:

  • If the box’s own writing mode is vertical, assume horizontal-tb.

  • If the box’s own writing mode is horizontal, assume vertical-lr if direction is ltr and vertical-rl if direction is rtl.

For the purposes of finding the baselines of a box, it and all its in-flow descendants with a scrolling mechanism (see the overflow property) must be considered as if scrolled to their initial scroll position. Additionally, if the position of a scroll container’s first/last baseline is outside its border edge, that baseline’s position is clamped to the border edge.

A baseline-sharing group is composed of boxes that participate in baseline alignment together. This is possible only if they both:

• Share an along an axis perpendicular to the axis they’re being baseline-aligned in. (For example, grid items with align-self: baseline are baseline-aligning along the grid’s block axis, and therefore participate with other items in their row.)
• Have compatible baseline alignment preferences (i.e., the baselines that want to align are on the same side of the alignment context).

Note: Boxes participating in baseline content-alignment and boxes participating in baseline self-alignment can be part of the same baseline-sharing group, and can thus align to each other. The difference between the two methods is in where extra space is inserted to perform the alignment (inside or outside the box’s own border).

Boxes share an , along a particular axis, and established by a particular box, when they are:

• table cells in the same row, along the table’s row (inline) axis, established by the row box
• grid items in the same row, along the grid’s row (inline) axis, established by the grid container
• grid items in the same column, along the grid’s column (block) axis, established by the grid container
• flex items in the same flex line, along the flex container’s main axis, established by the flex container

Note: Conceptually, the inline-level boxes in a line box also share a self-alignment context and participate in a baseline-sharing group; however they only baseline-align in response to the vertical-align property, not any of the properties defined in this module. See [CSS-INLINE-3].

If a box spans multiple , then it participates in first/last baseline alignment within its start-most/end-most along that axis. For example, a table cell spanning three rows participates in first-baseline alignment with the table cells in the first row that it spans, or alternatively in last-baseline alignment with the table cells in the last row that it spans.

The baseline alignment preferences of two boxes in a baseline-sharing group are compatible if they have:

• the same block flow direction and same baseline alignment preference

• opposite block flow direction and opposite baseline alignment preference

Given a set of alignment subjects and their baselines that all belong to a single baseline-sharing group, the alignment subjects are baseline-aligned as follows:

1. Generate the baseline-sharing group’s baseline table from the first available font of the group’s and overlay also the mirror of this baseline table by aligning their central baselines. These are the baseline “grids” to which the alignment subjects will align.

2. Align each alignment subject by its specified alignment baseline to the group’s baseline table or its mirror, whichever matches the alignment subject’s line orientation. Unless otherwise specified (e.g. via the alignment-baseline property), the alignment baseline is the dominant baseline of the .

3. Position the aligned baseline-sharing group within the alignment container according to its fallback alignment. The fallback alignment of a baseline-sharing group is the fallback alignment of its items as resolved to physical directions.

4. For first/last baseline content-alignment, then add the minimum necessary extra space between the alignment container’s start/end content edge and the alignment subject’s edge to align the start/end margin edges of all the alignment containers in the while maintaining baseline alignment within the baseline-sharing group.

When both inset properties in a given axis are auto on an absolutely positioned box, CSS2 uses its static position to resolve its size and position. See CSS2.1§10.3.7. The box alignment properties modify these calculations, just as they do the sizing and positioning calculations in other layout modes. These modifications refer to a static-position rectangle, whose edges represent the static position of the box from each side of its containing block.

The static-position rectangle and the static positions to which it corresponds are defined by the layout model of its “hypothetical box”:

Block Layout

The static positions of a block-level box are defined in [CSS2] Chapter 10. The static-position rectangle is a zero-thickness rectangle spanning between the inline-axis sides of the box’s static-position containing block (see CSS2§10.3.7); and positioned at its block-start static position (see CSS2§10.6.4).

Inline Layout

The static positions of an inline-level box are defined in [CSS2] Chapter 10. The static-position rectangle is a zero-thickness rectangle spanning between the line-over/line-under sides of the line box that would have contained its “hypothetical box” (see CSS2§10.3.7); and positioned at its inline-start static position.

Flex Layout

The static-position rectangle of the child of a flex container corresponds to the content edges of the flex container. See CSS Flexbox 1 § 4.1 Absolutely-Positioned Flex Children.

Grid Layout

By default, the static-position rectangle of the child of a grid container corresponds to the content edges of the grid container. However, if that grid container also establishes the box’s actual containing block, then the grid area specified by the grid-placement properties establishes its static-position rectangle instead. See the static position of a grid container child in [CSS-GRID-1].

Changes since the 17 February 2023 Working Draft include:

• Made block containers default to safe alignment. See § 4.4.1.3 All Other Alignment. (Issue 8992)
• Made absolutely positioned boxes default to using a “smart” safe alignment that allows unsafe overflow of the inset-modified containing block while maintaining safety within the original containing block. See § 4.4.1.2 Self-Alignment for Absolutely Positioned Boxes. (Issue 10316, Issue 9960)
• Make all the space-* keywords fallback to safe overflow. (Issue 10154)
• Clearly define the interaction of overflowing content distribution and scroll containers to not impact layout, but to only affect the extent of the scrollable overflow area. (Issue 4957)
• Only apply the special margin-edge baseline rule for scroll container block containers when baseline-source is its initial value. (Issue 8214)
• When synthesizing the baseline of an orthogonal-flow box, make the assumed parallel writing mode sensitive to direction. (Issue 7775)

  Otherwise, assume either horizontal-tb or vertical-lr writing-mode, whichever is orthogonal to the box’s own writing-mode.

  Otherwise:

  • If the box’s own writing mode is vertical, assume horizontal-tb.
  • If the box’s own writing mode is horizontal, assume vertical-lr if direction is ltr and vertical-rl if direction is rtl.

• Clarify that spanning cells only participate in the first/last row they span when participating in first/last baseline alignment. (Issue 7655)
• Define the grid-gap properties as legacy name aliases of the gap properties. (Issue 8014)
• Defer definition of normal alignment for absolutely positioned boxes to [css-position-3]. (Issue 11215, Issue 11285)
• Changed sentence about applicability of row-gap to multi-column containers to indicate that it applies in [CSS-MULTICOL-2]. (Issue 11539)
• Defined that gutters dissappear at fragmentation breaks. (Issue 11520)

Changes since the 24 December 2021 Working Draft include:

• Define the baselines of a multi-column container. (Issue 7856, Issue 7639)
• Use the writing mode of the static-position containing block when determining the static position. (Issue 7599, Issue 7612; Changes)
• Remove definition of special behavior for including padding in scrollable overflow for non-normal alignments since this is now defined unconditionally in [CSS-OVERFLOW-3]. (Issue 129)
• Minor clarifications:

  • Define fallback alignment of a baseline-sharing group as the shared fallback alignment of its individual items.

  • Annotate <length-percentage> value definitions using CSS bracketed range notation.

Changes since the 21 April 2020 Working Draft include:

• Allowed reordering of [ first | last ] and baseline components of <baseline-position>. (Issue 5235)
• Make fallback alignment of space-around and space-evenly include safe. (Issue 5088)
• Various corrections to normal alignment and percentage gaps to match respective layout specs.
• Corrections to special legacy handling of the last baseline set of scroll containers. (Issue 3611)
• Clarify that a box with no baseline set synthesizes its alignment baseline as needed. (Issue 3611)
• Clarified that only non-replaced boxes are affected by content distribution. (Issue 4545)
• Clarified when a box has a coordinated self-alignment preference that enables baseline content-alignment, particularly with respect to auto margins. (Issue 5923)
• Better define how baseline self-alignment and content-alignment interact. (Issue 6389)
• Clarify how baseline-sharing groups determine their fallback alignment. (Issue 7645)

Changes since the 6 December 2018 Working Draft include:

• Improved the center self-alignment of absolutely-positioned elements. Issue 4659
• Fixed inconsistent fallback of baseline alignment in mixed writing modes. Issue 3454
• Minor editorial fixes and clarifications.

Changes since the 30 August 2018 Working Draft consist of some minor clarifications.

Changes since the 23 April 2018 Working Draft include:

• Better definition of how the alignment properties interact with absolutely-positioned boxes with auto offsets. See § 6.1.2 Absolutely-Positioned Boxes, § 6.2.2 Absolutely-Positioned Boxes, § 6.5 Effects on Sizing of Absolutely Positioned Boxes with Static-Position Insets, and Appendix A: Static Position Terminology.
• More detailed definition of how the content-distribution properties work on scroll containers. See § 5.3 Alignment Overflow and Scroll Containers.
• Noted CSS2’s special rules about the baselines of inline-block scroll containers.
• Defined that percentage gaps compute against zero when calculating intrinsic sizes, and resolve during layout. (Issue 509)
• Miscellaneous minor clarifications.

Changes since the 6 September 2017 Working Draft include:

• Added more illustrations! Many thanks to Melanie Richards for working through a difficult diagramming problem.
• Fixed errors in property definition table of gap shorthand.
• Defining percentage gaps to resolve to zero when the containing block’s size depends on the gaps. (Issue 509, Issue 2297)
• Fixed errors in handling left and right in the grammars.
• Fixed discrepancy in space-align fallback alignment. (Issue 2316)
• Tightened up handling of baseline alignment in cases where the box edges don’t align. (Issue 1556, Issue 1611)
• Miscellaneous clarifications.

Changes since the 20 July 2017 Working Draft include:

• Added the row-gap and column-gap properties and gap shorthand, applying them to both grid layout and flex layout to replace the grid-specific grid-row-gap/grid-column-gap/grid-gap properties.

Changes since the 15 May 2017 Working Draft include:

• Dropped the left and right keywords from align-self and align-content. They may be re-introduced in a later level if there is demand. (Issue 1403)
• Assigned end fallback alignment to stretch cases when combined with last baseline content-alignment.
• Disabled baseline alignment across cells in a table column, due to implementation complexity.
• A large number of minor corrections and clarifications reported by David Baron.

Changes since the 7 April 2017 Working Draft include:

• Adding a section to clarify handling of partial implementations. (Issue 1167)
• Dropped <baseline-position> value of justify-content since it can’t do anything anyway. (Issue 1184)
• Deferred ability to specify fallback alignments to Level 4. (Issue 1002)
• Fixed position of <overflow-position> wrt <content-position>. (Issue 1001)
• Fixed rules for handling baseline-aligned boxes being aligned along their block axis. (Issue 1038)
• Renamed justify-items: auto to justify-items: legacy. (Issue 1318)
• Clamped baselines of scrollable boxes to the border edge, rather than margin edge. (Issue 766)

As a simple layout spec, this introduces no new privacy considerations.

As a simple layout spec, this introduces no new security considerations.

Special thanks goes to David Baron, Javier Fernandez, Markus Mielke, Alex Mogilevsky, and the participants in the CSSWG’s March 2008 F2F alignment discussions for their contributions to the alignment model described herein, and to Melanie Richards for her illustrations of the various alignment keywords.

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

Advisements are normative sections styled to evoke special attention and are set apart from other normative text with <strong class="advisement">, like this: UAs MUST provide an accessible alternative.

A style sheet is conformant to this specification if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.

A renderer is conformant to this specification if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by this specification by parsing them correctly and rendering the document accordingly. However, the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)

An authoring tool is conformant to this specification if it writes style sheets that are syntactically correct according to the generic CSS grammar and the individual grammars of each feature in this module, and meet all other conformance requirements of style sheets as described in this module.

So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported component values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored.

Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.

To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before releasing an unprefixed implementation of any CSS features. Testcases submitted to W3C are subject to review and correction by the CSS Working Group.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3