dt[style*="cursor"] * { cursor: inherit; }

.awesome-table td {padding:5px}

.awesome-table {color:#000;background:#fff;margin: auto;}

spec:css-overflow-3; type:property; text:overflow

spec:css21; type:property; text:display

spec:css21; type:property; text:width

spec:css21; type:property; text:height

spec:css21; type:property; text:left

spec:css21; type:property; text:overflow

spec:css21; type:property; text:border-bottom-width

spec:css21; type:property; text:border-left-width

spec:css21; type:property; text:border-right-width

spec:css21; type:property; text:border-top-width

spec:css21; type:property; text:border-style

spec:css21; type:property; text:border-width

spec:css21; type:property; text:background-image

<!-- Some of the following definitions have existing exported definitions from other specs,

but not from specs that are OK to link to from a CR -->

url: https://www.w3.org/TR/CSS2/box.html#border-edge; type: dfn; spec: CSS2; text: border edge

url: https://www.w3.org/TR/CSS2/visufx.html#propdef-overflow

type: property; spec: CSS2; text: overflow

type: value; spec: CSS2; text: visible; for: overflow

url: https://www.w3.org/TR/CSS2/visuren.html#position-props; type: property; spec: CSS2;

text: top

text: bottom

text: left

text: right

url: https://www.w3.org/TR/CSS2/visudet.html#the-width-property; type: value; spec: CSS2; for: width; text: auto

This module describes CSS properties which enable authors

to style user interface related properties and values.

<a href="https://www.w3.org/TR/REC-CSS1#anchor-pseudo-classes">Section 2.1 of CSS1</a> [[CSS1]]

and <a href="https://www.w3.org/TR/CSS2/ui.html">Chapter 18 of CSS2</a> [[CSS2]]

introduced several user interface related properties and values.

<a href="https://www.w3.org/TR/2000/WD-css3-userint-20000216">User Interface for CSS3 (16 February 2000)</a> introduced several new user interface related features.

This specification incorporates, extends, and supersedes them.

The purpose of this specification is to achieve the following objectives:

<li>Extend the user interface features in CSS2.1.

<li>Provide additional CSS mechanisms to augment or replace other

dynamic presentation related features in HTML.

This document defines new features not present in earlier specifications.

In addition, it replaces and supersedes the following:

<li><a href="https://www.w3.org/TR/CSS2/ui.html#cursor-props">Section 18.1</a>,

<a href="https://www.w3.org/TR/CSS2/ui.html#dynamic-outlines">section 18.4</a>,

and Information on the stacking of outlines defined in

of Cascading Style Sheets, level 2, revision 1 [[CSS2]]

Note: The semantics of property definition tables were first introduced in [[CSS2#property-defs]].

More up-to-date definitions can be found in

[[CSS-TRANSITIONS-1]],

[[CSS-VALUES-3]],

and [[CSS-CASCADE-4]].

For the reader's convenience,

this specification links directly to these terms where relevant.

This specification follows the <a href="https://www.w3.org/TR/CSS2/about.html#property-defs">CSS property definition conventions</a> from [[!CSS2]]

using the <a href="https://www.w3.org/TR/css-values-3/#value-defs">value definition syntax</a> from [[!CSS-VALUES-3]].

Value types not defined in this specification are defined in CSS Values &amp; 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 <a>CSS-wide keywords</a> as their property value.

For readability they have not been repeated explicitly.

<dd>This is the behavior of width and height as specified by CSS2.1.

The specified width and height (and respective min/max properties)

apply to the width and height respectively of the content box of the element.

The padding and border of the element are laid out

and drawn outside the specified width and height.</dd>

<dd>Length and percentages values for width and height (and respective min/max properties)

on this element determine the border box of the element.

That is, any padding or border specified on the element

is laid out and drawn inside this specified width and height.

The content width and height are calculated

by subtracting the border and padding widths of the respective sides

from the specified 'width'

and 'height' properties.

As the content width and height

<a href="https://www.w3.org/TR/CSS2/visudet.html#the-width-property">cannot be negative</a> ([[!CSS2]], section 10.2),

this computation is floored at 0.

Used values, as exposed for instance through getComputedStyle(), also refer to the border box.

Note: This is the behavior of width and height as commonly implemented

by legacy HTML user agents for replaced elements and input elements.

Note: In contrast to the length and percentage values,

the ''width/auto'' value of the 'width' and 'height' properties

(as well as other keyword values introduced by later specifications,

unless otherwise specified)

is not influenced by the 'box-sizing' property,

and always sets the size of the content box.

The following terms, whose definitions vary based on the computed value of 'box-sizing' are introduced:

<tr><th><th>''box-sizing: content-box''<th>''box-sizing: border-box''

<tr><th><dfn>min inner width</dfn><td>'min-width'<td>max(0, 'min-width' &minus; 'padding-left' &minus; 'padding-right' &minus; 'border-left-width' &minus; 'border-right-width')

<tr><th><dfn>max inner width</dfn><td>'max-width'<td>max(0, 'max-width' &minus; 'padding-left' &minus; 'padding-right' &minus; 'border-left-width' &minus; 'border-right-width')

<tr><th><dfn>min inner height</dfn><td>'min-height'<td>max(0, 'min-height' &minus; 'padding-top' &minus; 'padding-bottom' &minus; 'border-top-width' &minus; 'border-bottom-width')

<tr><th><dfn>max inner height</dfn><td>'max-height'<td>max(0, 'max-height' &minus; 'padding-top' &minus; 'padding-bottom' &minus; 'border-top-width' &minus; 'border-bottom-width')

The <a href="https://www.w3.org/TR/CSS2/visudet.html">Visual formatting model details</a> of [[!CSS2]] are written assuming ''box-sizing: content-box''. The following disambiguations are made to clarify the behavior for all values of 'box-sizing':

<li>In <a href="https://www.w3.org/TR/CSS2/visudet.html#blockwidth">10.3.3</a>, the second <q>width</q> in the following phrase is to be interpreted as <a spec="css21">content width</a>: <q>If 'width' is not ''width/auto'' and 'border-left-width' + 'padding-left' + 'width' + [...]</q>

<li>In <a href="https://www.w3.org/TR/CSS2/visudet.html#abs-non-replaced-width">10.3.7</a>, <q>width</q> is to be interpreted as <a spec="css21">content width</a> in the following equation: <q>'left' + 'margin-left' + 'border-left-width' + 'padding-left' + 'width' + [...]</q>

<li>In <a href="https://www.w3.org/TR/CSS2/visudet.html#min-max-widths">10.4</a>, <q>width</q>, <q>height</q>, <q>min-width</q>, <q>max-width</q>, <q>min-height</q> and <q>max-height</q> are respectively to be interpreted as <a spec="css21">content width</a>, <a spec="css21">content height</a>, <a>min inner width</a>, <a>max inner width</a>, <a>min inner height</a> and <a>max inner height</a> in the following phrases:

<ol>

<li><q>The tentative used width is calculated [...]</q>

<li><q>If the tentative used width is greater than 'max-width', the rules above are applied again, but this time using the computed value of 'max-width' as the computed value for 'width'.</q>

<li><q>If the resulting width is smaller than 'min-width', the rules above are applied again, but this time using the value of 'min-width' as the computed value for 'width'.</q>

<li><q>Select from the table the resolved height and width values for the appropriate constraint violation. Take the max-width and max-height as max(min, max) so that min ≤ max holds true. In this table w and h stand for the results of the width and height computations [...]</q>

<li>All instances of these words in the table

<li><q>Then apply the rules under "Calculating widths and margins" above, as if 'width' were computed as this value.</q>

</ol>

<li>In <a href="https://www.w3.org/TR/CSS2/visudet.html#abs-non-replaced-height">10.6.4</a>, <q>height</q> is to be interpreted as <a spec="css21">content height</a> in the following equation: <q>'top' + 'margin-top' + 'border-top-width' + 'padding-top' + 'height' + [...]</q>

<li>In <a href="https://www.w3.org/TR/CSS2/visudet.html#min-max-heights">10.7</a>, <q>width</q>, <q>height</q>, <q>min-height</q> and <q>max-height</q> are respectively to be interpreted as <a spec="css21">content width</a>, <a spec="css21">content height</a>, <a>min inner height</a> and <a>max inner height</a> in the following phrases:

<ol>

<li><q>The tentative used height is calculated [...]</q>

<li><q>If this tentative height is greater than 'max-height', the rules above are applied again, but this time using the value of 'max-height' as the computed value for 'height'.</q>

<li><q>If the resulting height is smaller than 'min-height', the rules above are applied again, but this time using the value of 'min-height' as the computed value for 'height'.</q>

<li><q>[...] use the algorithm under Minimum and maximum widths above to find the used width and height. Then apply the rules under "Computing heights and margins" above, using the resulting width and height as if they were the computed values.</q>

</ol>

<div class="example"><p style="display:none">Example(s):

This example uses box-sizing to evenly horizontally split

two divs with fixed size borders inside a div container,

which would otherwise require additional markup.

sample CSS:

div.container {

width:38em;

border:1em solid black;

}

div.split {

box-sizing:border-box;

width:50%;

border:1em silver ridge;

float:left;

}

sample HTML fragment:

&lt;div class="container"&gt;

&lt;div class="split"&gt;This div occupies the left half.&lt;/div&gt;

&lt;div class="split"&gt;This div occupies the right half.&lt;/div&gt;

&lt;/div&gt;

demonstration of sample CSS and HTML:

<div style="width:38em; border:1em solid black"><div style="box-sizing:border-box; width:50%; border:1em silver ridge; float:left">This div should occupy the left half.</div><div style="box-sizing:border-box; width:50%; border:1em silver ridge; float:left">This div should occupy the right half.</div>The two divs above should appear side by side, each (including borders) 50% of the content width of their container. If instead they are stacked one on top of the other then your browser does not support 'box-sizing'.

At times, style sheet authors may want to create outlines around

visual objects such as buttons, active form fields, image maps, etc.,

to make them stand out. Outlines differ from borders in the following

ways:

<li>Outlines do not take up space.

<li>Outlines may be non-rectangular.

<li>UAs often render outlines on elements in the :focus state.

The outline properties control the style of these dynamic outlines.

The stacking of the rendering of these outlines is explicitly left up to implementations to provide a better user experience per platform. This supersedes the stacking of outlines as defined in <a href="https://www.w3.org/TR/CSS2/zindex.html">Appendix E of CSS 2.1</a> [[CSS2]].

Keyboard users,

in particular people with disabilities

who may not be able to interact with the page in any other fashion,

depend on the outline being visible

on elements in the :focus state,

thus authors must not make the outline invisible on such elements

without making sure an alternative highlighting mechanism is provided.

The rendering of applying transforms to outlines is left explicitly undefined in CSS3-UI.

The outline created with the outline properties is drawn "over" a box,

i.e., the outline is always on top,

and doesn't influence the position or size of the box,

or of any other boxes.

Therefore, displaying or suppressing outlines does not cause reflow.

Outlines may be non-rectangular.

For example, if the element is broken across several lines,

the outline should be an outline or minimum set of outlines

that encloses all the element's boxes.

Each part of the outline should be fully connected

rather than open on some sides

(as borders on inline elements are when lines are broken).

The parts of the outline are not required to be rectangular.

To the extent that the outline follows the <a>border edge</a>,

it should follow the 'border-radius' curve.

The position of the outline may be affected by descendant boxes.

User agents should use an algorithm for determining

the outline that encloses a region appropriate

for conveying the concept of focus to the user.

Note: This specification does not define the exact position or shape of the outline, but it is typically drawn immediately outside the border box.

The 'outline-width' property accepts

the same values as

'border-width'

([[css-backgrounds-3#border-width]]).

The 'outline-style' property accepts

the same values as

'border-style'

([[css-backgrounds-3#border-style]]),

except that

<span class=css>hidden</span> is not a legal outline style.

In addition, in CSS3,

accepts the value ''outline-style/auto''.

The ''outline-style/auto'' value permits the user agent

to render a custom outline style,

typically a style which is either a user interface default for the platform,

or perhaps a style that is richer

than can be described in detail in CSS,

e.g. a rounded edge outline with semi-translucent outer pixels

that appears to glow.

As such, this specification does not define how the

is incorporated or used (if at all) when rendering

''outline-style/auto'' style outlines.

User agents may treat ''outline-style/auto'' as

''outline-style/solid''.

The 'outline-color' property

accepts all colors, as well as the keyword <dfn dfn-type=value for=outline-color>invert</dfn>.

''outline-color/Invert'' is expected to perform a color inversion on the pixels on the screen.

This is a common trick to ensure the focus border is visible,

regardless of color background.

Conformant UAs may ignore the ''outline-color/invert'' value

on platforms that do not support color inversion of the pixels on the screen.

If the UA does not support the ''outline-color/invert'' value

then it must reject that value at parse-time, and

the initial value of the 'outline-color' property

is the ''outline-color/currentColor'' keyword.

The 'outline' property is a shorthand property,

and sets all three of 'outline-style',

'outline-width',

and 'outline-color'.

Note: The outline is the same on all sides.

In contrast to borders,

there are no 'outline-top' or 'outline-left' etc. properties.

This specification does not define how multiple overlapping outlines are drawn,

or how outlines are drawn for boxes that are partially obscured behind other elements.

<div class="example"><p style="display:none">Example(s):

Here's an example of drawing a thick outline around a BUTTON element:

button { outline: thick solid }

Graphical user interfaces may use outlines around elements

to tell the user which element on the page has the focus.

These outlines are in addition to any borders,

and switching outlines on and off should not cause the document to reflow.

The focus is the subject of user interaction in a document

(e.g. for entering text or selecting a button).

<div class="example"><p style="display:none">Example(s):

For example, to draw a thick black line around an element when it has the focus,

and a thick red line when it is active,

the following rules can be used:

:focus { outline: thick solid black }

:active { outline: thick solid red }

Note: Since the outline does not affect formatting

(i.e., no space is left for it in the box model),

it may well overlap other elements on the page.

By default, the outline is drawn starting just outside the <a>border edge</a>.

However, it is possible to offset the outline and draw it beyond the <a>border edge</a>.

If the computed value of 'outline-offset'

is anything other than 0,

then the outline is outset from the <a>border edge</a> by that amount.

<div class="example"><p style="display:none">Example(s):

For example,

to leave 2 pixels of space between a focus outline

and the element that has the focus or is active,

the following rule can be used:

:focus,:active { outline-offset: 2px }

<p id=negative-offset>Negative values must cause the outline

to shrink into the border box.

Both the height and the width of outside of the shape

drawn by the outline should not become smaller

than twice the computed value of the 'outline-width' property,

to make sure that an outline can be rendered

even with large negative values.

User agents should apply this constraint

independently in each dimension.

If the outline is drawn as multiple disconnected shapes,

this constraint applies to each shape separately.

CSS2.1 provides a mechanism for controlling the appearance of a scrolling mechanism

(e.g. scrollbars)

on block container elements.

This specification adds to that a mechanism for controlling

user resizability of elements as well as the ability to specify text overflow behavior.

The 'resize' property allows the author

to specify whether or not an element is resizable by the user,

and if so, along which axis/axes.

<dt>none</dt>

<dd>The UA does not present a resizing mechanism on the element,

and the user is given no direct manipulation mechanism to resize the element.</dd>

<dt>both</dt>

<dd>The UA presents a bidirectional resizing mechanism

to allow the user to adjust both the height and the width of the element.</dd>

<dt>horizontal</dt>

<dd>The UA presents a unidirectional horizontal resizing mechanism

to allow the user to adjust only the width of the element.</dd>

<dt>vertical</dt>

<dd>The UA presents a unidirectional vertical resizing mechanism

to allow the user to adjust only the height of the element.</dd>

Currently it is possible to control the appearance of the scrolling mechanism (if any)

on an element using the 'overflow' property

(e.g. <code class="lang-css">overflow: scroll</code> vs. <code class="lang-css">overflow: hidden</code> etc.).

The purpose of the 'resize' property

is to allow control over the appearance and function of the resizing mechanism

(e.g. a resize box or widget) on the element.

Note: The resizing mechanism is NOT the same as the scrolling mechanism,

nor is it related to any UA mechanism for zooming.

The scrolling mechanism allows the user

to determine which portion of the contents of an element is shown.

The resizing mechanism allows the user

to determine the size of the element.

The 'resize' property applies to elements

that are <a>scroll containers</a>.

UAs may also apply it,

regardless of the value of the 'overflow' property,

to:

<li>Replaced elements representing images or videos, such as <{img}>, <{video}>, <{picture}>, <{svg}>, <{object}>, or <{canvas}>.

<li>The <{iframe}> element.

The effect of the 'resize' property on generated content is undefined. Implementations should not apply the 'resize' property to generated content.

Note: the 'resize' property may apply to generated content in the future if there is implementation of the {{CSSPseudoElement}} interface (See [[css-pseudo-4]]).

When an element is resized by the user,

the user agent sets

the 'width' and 'height' properties

to px unit length values of the size indicated by the user,

in the element’s <a href="https://www.w3.org/TR/css-style-attr/#style-attribute">style attribute</a> DOM,

replacing existing property declaration(s), if any,

without ''!important'', if any.

If an element is resized in only one dimension,

only the corresponding property is set, not both.

The precise direction of resizing

(i.e. altering the top left of the element or altering the bottom right)

may depend on a number of CSS layout factors

including whether the element is absolutely positioned,

whether it is positioned using the 'right'

and 'bottom' properties,

whether the language of the element is right-to-left etc.

The UA should consider the direction of resizing

(as determined by CSS layout),

as well as platform conventions and constraints when deciding

how to convey the resizing mechanism to the user.

The user agent must allow the user to resize the element

with no other constraints than what is imposed by

'min-width', 'max-width', 'min-height', and 'max-height'.

Note: There may be situations where user attempts to resize an element

appear to be overridden or ignored, e.g. because of ''!important'' cascading declarations that supersede

that element’s <a href="https://www.w3.org/TR/css-style-attr/#style-attribute">style attribute</a>

'width' and 'height' properties in the DOM.

Changes to the computed value of an element's 'resize' property

do not reset changes to the <a href="https://www.w3.org/TR/css-style-attr/#style-attribute">style attribute</a> made due to

user resizing of that element.

<div class="example"><p style="display:none">Example(s):

For example,

to make iframes scrollable <em>and</em> resizable,

the following rule can be used:

iframe,object[type^="text/"],

object[type$="+xml"],object[type="application/xml"]

{

overflow:auto;

resize:both;

}

<!--

too bad we don't have @viewport yet. otherwise this would be cool:

@viewport {

width: 100px;

height: 100px;

overflow: hidden;

resize: none

} /* display content in a non-resizable 100px by 100px window */

-->

This property specifies rendering when inline content overflows

its <a>end</a> line box edge

in the inline progression direction of its block container element ("the block")

that has 'overflow'

other than ''visible''.

<!-- REVIEW: I *think* this should not include ''overflow/clip'' -->

Text can overflow for example when it is prevented from wrapping

(e.g. due to <code class="lang-css">white-space: nowrap</code>

or a single word is too long to fit).

Values have the following meanings:

<dt><dfn id=overflow-clip dfn-type=value>clip</dfn></dt>

<dd>Clip inline content that overflows its block container element. Characters may be only partially rendered.</dd>

<dt><dfn id=overflow-ellipsis dfn-type=value>ellipsis</dfn></dt>

<dd>

Render an ellipsis character (U+2026)

to represent clipped inline content.

Implementations may substitute a more language, script, or writing-mode appropriate

ellipsis character,

or three dots "..." if the ellipsis character is unavailable.

The term "character" is used in this property definition

for better readability and means "grapheme cluster" [[!UAX29]]

for implementation purposes.

For the ellipsis value

implementations must hide characters and

at the <a>end</a> edge of the line as necessary to fit the ellipsis, and

place the ellipsis immediately adjacent

to the <a>end</a> edge of the remaining inline content.

The first character or

on a line

must be clipped rather than ellipsed.

These examples demonstrate which characters get hidden

to make room for the ellipsis in a bidi situation:

those visually at the end edge of the line.

Sample CSS:

div {

font-family: monospace;

white-space: pre;

overflow: hidden;

width: 9ch;

text-overflow: ellipsis;

}

Sample HTML fragments, renderings, and your browser:

<thead><th>HTML<th>Reference rendering<th>Your Browser</thead>

<td><code highlight=html>&lt;div>שלום 123456&lt;/div></code><td><div style="font-family:monospace">123456 ם…</div><td><div style="font-family: monospace; white-space: pre; overflow: hidden; width: 9ch; text-overflow: ellipsis">שלום 123456</div>

<tr><td><code highlight=html>&lt;div dir=rtl>שלום 123456&lt;/div></code><td><div style="font-family:monospace">…456 שלום</div><td><div style="font-family: monospace; white-space: pre; overflow: hidden; width: 9ch; text-overflow: ellipsis" dir=rtl>שלום 123456</div>

Ellipsing only affects rendering and must not affect layout

nor dispatching of pointer events:

The UA should dispatch any pointer event on the ellipsis to the elided element,

as if 'text-overflow' had been ''text-overflow/none''.

The ellipsis is styled and baseline-aligned according to

the block.

Ellipsing occurs after relative positioning and other graphical transformations.

If there is insufficient space for the ellipsis,

then clip the rendering of the ellipsis itself

(on the same side that neutral characters on the line

would have otherwise been clipped with the ''text-overflow:clip'' value).

<li>When the user is interacting with content

(e.g. editing, selecting, scrolling),

the user agent may treat ''text-overflow: ellipsis'' as ''text-overflow: clip''.

<li>Selecting the ellipsis should select the ellipsed text.

If all of the ellipsed text is selected,

UAs should show selection of the ellipsis.

Behavior of partially-selected ellipsed text is up to the UA.

<div class="example"><p style="display:none">Example(s):

These examples demonstrate setting the text-overflow of a block container element

that has text which overflows its dimensions:

sample CSS for a div:

<pre><code class="lang-css">div {

font-family:Helvetica,sans-serif; line-height:1.1;

width:3.1em; padding:.2em; border:solid .1em black; margin:1em 0;

}</code></pre>

sample HTML fragments, renderings, and your browser:

<tr><th>HTML</th><th>sample rendering</th><th>your browser</th></tr>

<td><pre><code class="lang-markup">&lt;div&gt;

CSS IS AWESOME, YES

&lt;/div&gt;

First, a box with text drawing outside of it.

<div style="width:3.1em; border:solid .1em black; margin:1em 0; padding:.2em; font-family:Helvetica,sans-serif; line-height:1.1;">CSS IS AWESOME, YES</div>

<td><pre><code class="lang-markup">&lt;div style="<strong>text-overflow:clip;</strong> overflow:hidden"&gt;

CSS IS AWESOME, YES

&lt;/div&gt;

Second, a similar box with the text clipped outside the box.

<div style="width:3.1em; border:solid .1em black; margin:1em 0; padding:.2em; font-family:Helvetica,sans-serif; line-height:1.1; overflow:hidden;text-overflow:clip;">CSS IS AWESOME, YES</div>

<td><pre><code class="lang-markup">&lt;div style="<strong>text-overflow:ellipsis;</strong> overflow:hidden"&gt;

CSS IS AWESOME, YES

&lt;/div&gt;

Third, a similar box with an ellipsis representing the clipped text.

<div style="width:3.1em; border:solid .1em black; margin:1em 0; padding:.2em; font-family:Helvetica,sans-serif; line-height:1.1; overflow:hidden;text-overflow:ellipsis;">CSS IS AWESOME, YES</div>

<td><pre><code class="lang-markup">&lt;div style="<strong>text-overflow:ellipsis;</strong> overflow:hidden"&gt;

NESTED

&lt;p&gt;PARAGRAPH&lt;/p&gt;

WON'T ELLIPSE.

&lt;/div&gt;

Fourth, a box with a nested paragraph demonstrating anonymous block boxes equivalency and non-inheritance into a nested element.

<div style="width:3.1em; border:solid .1em black; margin:1em 0; padding:.2em; font-family:Helvetica,sans-serif; line-height:1.1; overflow:hidden;text-overflow:ellipsis;">NESTED

<p>PARAGRAPH</p>

WON'T ELLIPSE.</div>

Note: the side of the line that the ellipsis is placed depends on the 'direction' of the block.

E.g. an overflow hidden right-to-left

(<code class="lang-css">direction: rtl</code>)

block clips inline content on the <a spec=css-writing-modes-3>left</a> side,

thus would place a text-overflow ellipsis on the <a spec=css-writing-modes-3>left</a>

to represent that clipped content.

<!-- insert RTL example diagram here to illustrate note. -->

This section applies to elements with text-overflow other than ''text-overflow:clip''

(non-clip text-overflow)

and overflow:scroll.

When an element with non-clip text-overflow has overflow of scroll

in the inline progression dimension of the text,

and the browser provides a mechanism for scrolling

(e.g. a scrollbar on the element,

or a touch interface to swipe-scroll, etc.),

there are additional implementation details that provide a better user experience:

When an element is scrolled (e.g. by the user, DOM manipulation),

more of the element's content is shown.

The value of text-overflow should not affect

whether more of the element's content is shown or not.

If a non-clip text-overflow is set,

then as more content is scrolled into view,

implementations should show whatever additional content fits,

only truncating content which would otherwise be clipped

(or is necessary to make room for the ellipsis/string),

until the element is scrolled far enough

to display the edge of the content

at which point that content should be displayed

rather than an ellipsis/string.

<div class="example"><p style="display:none">Example(s):

This example uses text-overflow on an element with overflow scroll

to demonstrate the above described behavior.

sample CSS:

div.crawlbar {

text-overflow: ellipsis;

height: 2em;

overflow: scroll;

white-space: nowrap;

width: 15em;

border:1em solid black;

}

sample HTML fragment:

&lt;div class="crawlbar"&gt;

CSS is awesome, especially when you can scroll

to see extra text instead of just

having it overlap other text by default.

&lt;/div&gt;

demonstration of sample CSS and HTML:

CSS is awesome, especially when you can scroll

to see extra text instead of just

having it overlap other text by default.

</div> <!-- example -->

While the content is being scrolled, implementations may adjust their rendering of ellipses (e.g. align to the box edge rather than line edge).

This property specifies the type of cursor to be displayed for the pointing device

when the cursor's hotspot is within the element's <a>border edge</a>.

Note: As per [[css-backgrounds-3#border-radius]], the <a>border edge</a> is affected by 'border-radius'.

In the case of overlapping elements,

which element determines the type of cursor

is based on hit testing:

the element determining the cursor

is the one that would receive a click

initiated from this position.

Note: The specifics of hit testing

are out of scope of this specification.

Hit testing will hopefully be defined

in a future revision of CSS or HTML.

User agents may ignore the cursor property over native user-agent controls such as scrollbars, resizers, or other native UI widgets e.g. those that may be used inside some user agent specific implementations of form elements.

User agents may also ignore the cursor property

and display a cursor of their choice

to indicate various states of the UA's user interface,

such as a busy cursor when the page is not responding,

or a text cursor when the user is performing text selection.

Note: [[HTML]] defines <a href="https://html.spec.whatwg.org/multipage/rendering.html#image-maps-2">special handling of image maps</a>

for the 'cursor' property.

Values have the following meanings:

#cursors dfn { cursor: inherit }

<dt>image cursors

<dd>The user agent retrieves the cursor from the resource designated by the URI.

If the user agent cannot handle the first cursor of a list of cursors,

it must attempt to handle the second, etc.

If the user agent cannot handle any user-defined cursor,

it must use the cursor keyword at the end of the list.

Conforming user agents may, instead of <<url>>, support <<image>> which is a superset.

The UA must support the following image file formats: