button { outline: thick solid }
	

	:focus  { outline: thick solid black }
	:active { outline: thick solid red }
	

Offsetting the Outline: the 'outline-offset' property

Name: outline-offset
Value: <>
Initial: 0
Applies to: all elements
Inherited: no
Percentages: N/A
Media: visual
Computed value: <> value in absolute units (px or physical).
Animation Type: length

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

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.

Resizing & Overflow

Resizing Boxes: the 'resize' property

Name: resize
Value: none | both | horizontal | vertical
Initial: none
Applies to: elements with 'overflow' other than visible,
 and optionally replaced elements such as images, videos, and iframes
Inherited: no
Percentages: N/A
Media: visual
Computed value: as specified

none

The UA does not present a resizing mechanism on the element, and the user is given no direct manipulation mechanism to resize the element.

both

The UA presents a bidirectional resizing mechanism to allow the user to adjust both the height and the width of the element.

horizontal

The UA presents a unidirectional horizontal resizing mechanism to allow the user to adjust only the width of the element.

vertical

The UA presents a unidirectional vertical resizing mechanism to allow the user to adjust only the height of the element.

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

	iframe,object[type^="text/"],
	object[type$="+xml"],object[type="application/xml"]
	{
	  overflow:auto;
	  resize:both;
	}
	

Overflow Ellipsis: the 'text-overflow' property

Name: text-overflow
Value: [ clip | ellipsis | <> | fade | <> ]{1,2}
Initial: clip
Applies to: block containers
Inherited: no
Percentages: refer to the width of the line box
Media: visual
Computed value: As specified, with <> converted to absolute units

clip

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

ellipsis

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.

<>

Render the given string to represent clipped inline content. The given string is treated as an independent paragraph for bidi purposes.

fade( <> | <> )

Clip inline content that overflows its line box. Characters may be only partially rendered. In addition, the UA must apply a fade out effect near the edge of the line box, reaching complete transparency at the edge. Issue: Do we need to define the way the fade out is calculated so that the fading is identical across browsers? It should probably be something like ''mask-image: linear-gradient(to right, rgba(0,0,0,1), rgba(0,0,0,0))'', except applied to the relevant portion of the line only. The argument determines the distance over which the fade effect is applied. The <> is resolved against the width of the line box. Values lower than 0 are clipped to 0. Values greater than the width of the line box are clipped to the width of the line box. Issue: If the line box is too short to display the fade effect at the desired length, should we drop the effect, or shrink the distance it is applied over until it fits, or clip the end of the fade? Issue: How should we deal with things overflowing out of the line box, or overlapping onto it? Should fade apply to the logical content of the line, or to the physical area of the line box, or the intersection of both?

fade

Same as ''fade()'', but the distance over which the fading effect is applied is determined by the UA. ''1em'' is suggested as a reasonable value.

div {
  font-family: monospace;
  white-space: pre;
  overflow: hidden;
  width: 9ch;
  text-overflow: ellipsis;
}

ellipsing details

• 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).

user interaction with ellipsis

• When the user is interacting with content (e.g. editing, selecting, scrolling), the user agent may treat ''text-overflow/ellipsis'', string values, ''overflow-text/fade'' or ''overflow-text/fade()'' as ''text-overflow:clip''.
• 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 {
		font-family: Helvetica, sans-serif;
		line-height: 1.1;
		width: 3.1em;
		border: solid .1em black;
		padding: 0.2em; margin:1em 0;
	}
	

			<div>
			CSS IS AWESOME, YES
			</div>
			

			<div style="text-overflow:clip; overflow:hidden">
			CSS IS AWESOME, YES
			</div>
			

			<div style="text-overflow:ellipsis; overflow:hidden">
			CSS IS AWESOME, YES
			</div>
			

			<div style="text-overflow:ellipsis; overflow:hidden">
			NESTED
			 <p>PARAGRAPH</p>
			WON'T ELLIPSE.
			</div>
			

			<div style="text-overflow:fade; overflow:hidden">
			CSS IS AWESOME, YES
			</div>
			

ellipsis interaction with scrolling interfaces

	div.crawlbar {
		text-overflow: ellipsis;
		height: 2em;
		overflow: scroll;
		white-space: nowrap;
		width: 15em;
		border:1em solid black;
	}
	

	<div class="crawlbar">
	CSS is awesome, especially when you can scroll
	to see extra text instead of just
	having it overlap other text by default.
	</div>
	

Pointing Devices and Keyboards

Pointer interaction

Styling the Cursor: the 'cursor' property

Name: cursor
Value: [ [<> [<x> <y>]?,]* 

 [ auto | default | none |

 context-menu | help | pointer | progress | wait | 

 cell | crosshair | text | vertical-text | 

 alias | copy | move | no-drop | not-allowed | grab | grabbing | 

 e-resize | n-resize | ne-resize | nw-resize | s-resize | se-resize | sw-resize | w-resize |
 ew-resize | ns-resize | nesw-resize | nwse-resize |
 col-resize | row-resize |
 all-scroll |

 zoom-in | zoom-out 

 ] ]
Initial: auto
Applies to: all elements
Inherited: yes
Percentages: N/A
Media: visual, interactive
Computed value: as specified, except with any relative URLs converted to absolute

image cursors

<>

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 <>, support <> which is a superset. The UA must support the following image file formats:

• PNG, as defined in [[!PNG]]
• SVG, as defined in [[!SVG11]], in secure static mode [[!SVG2]], if it has an intrinsic size.
• any other non-animated image file format that they support for <> in other properties, such as the the 'background-image' property

In addition, the UA should support the following image file formats:

• SVG, as defined in [[!SVG11]], in secure animated mode [[!SVG2]], if it has an intrinsic size.
• any other animated image file format that they support for <> in other properties, such as the the 'background-image' property

The UA may also support additional file formats, including SVG, as defined in [[!SVG11]], in secure static mode or secure animated mode [[!SVG2]], even if it does not have an intrinsic size. Note: The CSS Working group initially intended support for all SVG, intrinsically sized or not. Support for non intrinsically sized SVG was downgraded from mandatory to optional due to lack of implementations. Note: At the time of writing this specification (spring 2015), the only file formats supported for cursors in common desktop browsers are the .ico and .cur file formats, as designed by Microsoft. For compatibility with legacy content, UAs are encouraged to support these, even though the lack of an open specification makes it impossible to have a normative requirement about these formats. Some information on these formats can be found on Wikipedia. The default object size for cursor images is a UA-defined size that should be based on the size of a typical cursor on the UA's operating system. The concrete object size is determined using the default sizing algorithm. If an operating system is incapable of rendering a cursor above a given size, cursors larger than that size must be shrunk to within the OS-supported size bounds, while maintaining the cursor image's intrinsic ratio, if any. The optional <x> and <y> coordinates identify the exact position within the image which is the pointer position (i.e., the hotspot).

<x>

<y>

Each is a <>. The x-coordinate and y-coordinate of the position in the cursor's coordinate system (left/top relative) which represents the precise position that is being pointed to. Note: This specification does not define how the coordinate systems of the various types of <> are established, and defers these definitions to [[CSS4-IMAGES]]. If the values are unspecified, then the intrinsic hotspot defined inside the image resource itself is used. If both the values are unspecific and the referenced cursor has no defined hotspot, the effect is as if a value of "0 0" were specified. If the coordinates of the hotspot, as specified either inside the image resource or by <x> and <y> values, fall outside of the cursor image, they must be clamped (independently) to fit.

general purpose cursors

auto

The UA determines the cursor to display based on the current context. Specifically, ''cursor/auto'' behaves as ''cursor/text'' over selectable text or editable elements, and ''cursor/default'' otherwise.

default

The platform-dependent default cursor. Often rendered as an arrow.

none

No cursor is rendered for the element.

links and status cursors

context-menu

A context menu is available for the object under the cursor. Often rendered as an arrow with a small menu-like graphic next to it.

help

Help is available for the object under the cursor. Often rendered as a question mark or a balloon.

pointer

The cursor is a pointer that indicates a link. Often rendered as the backside of a hand with the index finger extended.

progress

A progress indicator. The program is performing some processing, but is different from ''wait'' in that the user may still interact with the program. Often rendered as a spinning beach ball, or an arrow with a watch or hourglass.

wait

Indicates that the program is busy and the user should wait. Often rendered as a watch or hourglass.

selection cursors

cell

Indicates that a cell or set of cells may be selected. Often rendered as a thick plus-sign with a dot in the middle.

crosshair

A simple crosshair (e.g., short line segments resembling a "+" sign). Often used to indicate a two dimensional bitmap selection mode.

text

Indicates text that may be selected. Often rendered as a vertical I-beam. User agents may automatically display a horizontal I-beam/cursor (e.g. same as the ''vertical-text'' keyword) for vertical text, or for that matter, any angle of I-beam/cursor for text that is rendered at any particular angle.

vertical-text

Indicates vertical-text that may be selected. Often rendered as a horizontal I-beam.

drag and drop cursors

alias

Indicates an alias of/shortcut to something is to be created. Often rendered as an arrow with a small curved arrow next to it.

copy

Indicates something is to be copied. Often rendered as an arrow with a small plus sign next to it.

move

Indicates something is to be moved.

no-drop

Indicates that the dragged item cannot be dropped at the current cursor location. Often rendered as a hand or pointer with a small circle with a line through it.

not-allowed

Indicates that the requested action will not be carried out. Often rendered as a circle with a line through it.

grab

Indicates that something can be grabbed (dragged to be moved). Often rendered as the backside of an open hand.

grabbing

Indicates that something is being grabbed (dragged to be moved). Often rendered as the backside of a hand with fingers closed mostly out of view.

resizing and scrolling cursors

e-resize, n-resize, ne-resize, nw-resize, s-resize, se-resize, sw-resize, w-resize

Indicates that some edge is to be moved. For example, the ''se-resize'' cursor is used when the movement starts from the south-east corner of the box.

ew-resize, ns-resize, nesw-resize, nwse-resize

Indicates a bidirectional resize cursor.

col-resize

Indicates that the item/column can be resized horizontally. Often rendered as arrows pointing left and right with a vertical bar separating them.

row-resize

Indicates that the item/row can be resized vertically. Often rendered as arrows pointing up and down with a horizontal bar separating them.

all-scroll

Indicates that the something can be scrolled in any direction. Often rendered as arrows pointing up, down, left, and right with a dot in the middle.

zooming cursors

zoom-in, zoom-out

Indicates that something can be zoomed (magnified) in or out, and often rendered as a magnifying glass with a "+" or "-" in the center of the glass, for ''zoom-in'' and ''zoom-out'' respectively.

	:link,:visited {
	    cursor: url(example.svg#linkcursor),
		    url(hyper.cur),
		    url(hyper.png) 2 3,
		    pointer
	}
	

Cursor of the canvas

Insertion caret

Coloring the Insertion Caret: the 'caret-color' property

Name: caret-color
Value: auto | <>
Initial: auto
Applies to: all elements
Inherited: yes
Percentages: N/A
Media: interactive
Computed value: The computed value for ''caret-color/auto'' is ''caret-color/auto''.
 For <> values, see resolving color values in [[!CSS-COLOR-4]].
Animation Type: color

auto

User agents should use ''currentColor''. User agents may automatically adjust the color of caret to ensure good visibility and contrast with the surrounding content, possibly based on the currentColor, background, shadows, etc. Note: When 'caret-shape' is ''caret-shape/block'', ensuring good visibility and contrast is best achieved with a UA determined color other than ''currentColor''.

<>

The insertion caret is colored with the specified color.

Shape of the insertion caret: 'caret-shape'

Name: caret-shape
Value: auto | bar | block | underscore
Initial: auto
Applies to: elements that accept input
Inherited: yes
Percentages: N/A
Media: interactive
Computed value: Same as specified value
Animatable: no

auto

The UA determines the shape of the caret. It should match platform conventions, and may be adjusted based on context. For example, if a UA switches between insert mode and overtype mode when the user presses the insert key on their keyboard, it may show a ''caret-shape/bar'' caret in insert mode, and a ''caret-shape/block'' caret in overtype mode.

bar

The UA must render the text insertion caret as a thin bar placed at the insertion point. This means it is between, before, or after characters, not over them. It should be perpendicular to the inline progression direction, although UAs may render it slanted when inserting italic or oblique text.

block

The UA must render the text insertion caret as a rectangle overlapping the next visible character following the insertion point. If there is no visible character after the insertion point, the UA must render the caret after the last visible character. UAs may render it as a slanted rectangle when inserting italic or oblique text.

underscore

The UA must render the text insertion caret as a thin line under (as defined in [[!CSS-WRITING-MODES-3]] the next visible character following the insertion point. If there is no visible character after the insertion point, the UA must render the caret after the last visible character.

• The caret must not be obscured by the background of the element
• UAs must render ''caret-shape/block'' carets so that the character it overlaps with is not obscured by the caret

	.console {
		caret-shape: underscore;
		background: black;
		color: white;
		font-family: monospace;
		padding: 1ex;
	}
	

	user@host:css-ui-4 $ ls -a
	. .. Overview.bs Overview.html
	user@host:css-ui-4 $  
	

	user@host:css-ui-4 $ ls -a
	. .. Overview.bs Overview.html
	user@host:css-ui-4 $
	

Insertion caret shorthand: 'caret'

Name: caret
Value: <<'caret-color'>> || <<'caret-shape'>>
Initial: auto
Applies to: elements that accept input
Inherited: yes
Percentages: N/A
Media: interactive
Computed value: See individual properties
Animatable: See individual properties

Keyboard control

Directional Focus Navigation: the 'nav-up', 'nav-right', 'nav-down', 'nav-left' properties

Name: nav-up , nav-right , nav-down , nav-left
Value: auto | <> [ current | root | <> ]?
Initial: auto
Applies to: all enabled elements
Inherited: no
Percentages: N/A
Media: interactive
Computed value: as specified

auto

The user agent automatically determines which element to navigate the focus to in response to directional navigational input.

<>

The <> value is an ID selector [[SELECT]]. In response to directional navigation input corresponding to the property, the focus is navigated to the first element in tree order matching the selector. If this refers to the currently focused element, the directional navigation input respective to the nav- property is ignored — there is no need to refocus the same element. If no element matches the selector, the user agent automatically determines which element to navigate the focus to. If the focus is navigated to an element that was not otherwise focusable, it becomes focusable only as the result of this directional navigation, and the :focus pseudo-class matches the element while it is focused as such. Note: there were other options under consideration for such "not otherwise focusable" elements, including focus to the next otherwise focusable element in the document tree (including descendants of such a not otherwise focusable element). Input on such other options is welcome and explicitly solicited, especially from implementation experiences and author experience using the directional navigation properties in their content.

<>

The <target-name> parameter indicates the target frame for the focus navigation. It is a <> and it MUST NOT start with the underscore "_" character. Error handling: if it does start with an underscore, "_parent" navigates to the parent frame, "_root" is treated as ''root'', and other values navigate to a frame by that name if it exists. If the specified target frame does not exist, the parameter will be treated as the keyword ''current'', which means to simply use the frame that the element is in. The keyword ''root'' indicates that the user agent should target the full window.

	button { position:absolute }

	button#b1 {
		top:0; left:50%;
		nav-right:#b2; nav-left:#b4;
		nav-down:#b2; nav-up:#b4;
	}

	button#b2 {
		top:50%; left:100%;
		nav-right:#b3; nav-left:#b1;
		nav-down:#b3; nav-up:#b1;
	}

	button#b3 {
		top:100%; left:50%;
		nav-right:#b4; nav-left:#b2;
		nav-down:#b4; nav-up:#b2;
	}

	button#b4 {
		top:50%; left:0;
		nav-right:#b1; nav-left:#b3;
		nav-down:#b1; nav-up:#b3;
	}
	

	button#foo { nav-left: #bar "sidebar"; }
	

Obsolete: the ime-mode property

input[type=password] {
		ime-mode: auto !important;
	}
	

User Interaction

Controlling content selection

	Name: user-select
	Value: auto | text | none | contain | all
	Initial: auto
	Inherited: no
	Applies to: all elements, and optionally to the ''::before'' and ''::after'' pseudo elements
	Media: interactive
	Computed value: See below

1. on editable elements where the computed value is always ''user-select/contain'' regardless of the specified value
2. when the specified value is ''user-select/auto'', which computes one of the other values as defined below

auto

The computed value of ''user-select/auto'' is determined as follows:

• On the ''::before'' and ''::after'' pseudo elements, the computed value is ''user-select/none''
• If the element is an editable element, the computed value is ''user-select/contain''
• Otherwise, if the computed value of 'user-select' on the parent of this element is ''all'', the computed value is ''all''
• Otherwise, if the computed value of 'user-select' on the parent of this element is ''user-select/none'', the computed value is ''user-select/none''
• Otherwise, the computed value is ''user-select/text''

Note: This unusual combination of a non inherited property with an initial value of ''user-select/auto'' whose computed value depends on the parent element makes it possible to create what is effectively selective inheritance. This was initially proposed by Microsoft in IE to introduce a behavior similar to inheritance except that the ''user-select/contain'' value does not inherit.

text

The element imposes no constraint on the selection.

none

The UA must not allow selections to be started in this element. A selection started outside of this element must not end in this element. If the user attempts to create such a selection, the UA must instead end the selection range at the element boundary. Note: As of the time of writing, experimental implementations do not all behave like this. Firefox does. Chrome and Safari almost do: for a selection started after the element and trying to go backwards into the element they behave as specified here, but for a selection started before the element and trying to go into the element they behave as if the element has ''all'' and select it entirely. IE does not restrict selections started outside of the element from going into it at all. Another difference is that in Chrome and Safari, if the user attempts to start a selection inside a ''user-select: none'', and to end the selection out of it, a selection will be created from the boundary of the element to the user-designated end-point. Firefox and Internet explorer behave as prescribed in this specification and do not create a selection at all. However, if this element has descendants on which the computed value of 'user-select' is not ''user-select/none'', selections that start and end within these descendants are allowed. The UA must allow selections to extend across this element, and must exclude this element from such a selection. An exception is made for UAs which do not support multiple ranges per selection, and they may include this element. If the element has descendants on which 'user-select' does not compute to ''user-select/none'', these descendants must be included in a selection extending across the element. This specification makes no normative requirement about the behavior of the clipboard. however, UAs are encouraged to keep the visual selection consistent with what would get copied to the clipboard when copying. Copying text that does not appear to be selected, or vice versa, is highly confusing to users. Attempting to start a selection in an element where 'user-select' is ''user-select/none'', such as by clicking in it or starting a drag in it, must not cause a pre-existing selection to become unselected or to be affected in any way. As 'user-select' is a UI convenience mechanism, not a copy protection mechanism, the UA may provide an alternative way for the user to explicitly select the text even when 'user-select' is ''user-select/none''. Note: ''user-select/none'' is not a copy protection mechanism, and using it as such is ineffective: User Agents are allowed to provide ways to bypass it, it will have no effect on legacy User Agents that do not support it, and the user can disable it through the user style sheet or equivalent mechanisms on UAs that do anyway. Instead, ''user-select/none'' is meant to make it easier for the user to select the content they want, by letting the author disable selection on UI elements that are not useful to select. Tools such as CSS validators, linters or in-browser developer tools are encouraged to use heuristics to detect and warn against incorrect or abusive usage that would hamper usability or violate common user expectations.

Authors should be careful about not constraining the user unnecessarily. For example, setting ''user-select: none'' on the root element, and relaxing that restriction on a handful of elements the author judges useful to select can be frustrating to users: * Clicking in empty areas to undo the current selection will no longer be effective * The author may have overlooked some areas which should be selectable * Areas may be added later to the page without remembering to make them selectable * The user may want to select pieces of text other than the main content, for instance to look them up in a dictionary or in some translation tool, or to look for warnings and error messages in a search engine… Instead, a good practice is for authors is to selectively apply ''user-select: none'' to elements which seem likely to be accidentally selected when doing so would interfere with the more likely intended action. Accidentally leaving parts of the page that are unlikely to be interacted with selectable will likely cause much less frustration to users than the opposite.

contain

UAs must not allow a selection which is started in this element to be extended outside of this element. A selection started outside of this element must not end in this element. If the user attempts to create such a selection, the UA must instead end the selection range at the element boundary. The UA must allow selections to extend across this element, and such selections must include the content of the element. Note: At the time of writing, experimental implementations behave differently from eachother about selections started outside and selections going into the element. The behavior can be observed even on browsers that do not explicitly support ''user-select/contain'' by trying to select into a <{textarea}> or a contenteditable element. Note: This was initially introduced as an experimental feature in Internet Explorer, under the name user-select: element.

all

The content of the element must be selected atomically: If a selection would contain part of the element, then the selection must contain the entire element including all its descendants. If the element is selected and the computed value of 'user-select' on its parent is ''all'', then the parent must be included in the selection, recursively. If this element has descendants on which the computed value of 'user-select' is not ''all'' and if a selection is entirely contained in these descendants, then the selection is not extended to include this whole element.

button, meter, progress, select { user-select: none; }

Form Control Styling

Switching appearance

	input { appearance: none; }
	input[type=checkbox] { appearance: checkbox; }
	

Name: appearance
Value: auto | none
Initial: auto
Applies To: all elements
Inherited: no
Computed value: As specified
Media: all

auto

UAs may render form controls using native controls of the host operating system or with a look and feel not otherwise expressible in CSS. Elements other than form controls must be rendered as if ''appearance/none'' had been specified.

none

The element is rendered following the usual rules of CSS. Replaced elements other than form controls are not affected by this, and remain replaced elements. Form controls are not made to look like native controls of the host operating system. See below for details. Issue: Shouldn't this be called "normal" instead? ''appearance/none'' makes it sound like the targeted element will disappear.

• 'appearance'
• 'display'
• 'visibility'
• 'position'
• 'top'
• 'right'
• 'bottom'
• 'left'
• 'float'
• 'clear'
• 'margin' and related long-hand properties
• 'unicode-bidi'
• 'direction'
• 'all' This does not imply a requirement to apply all the properties reset by 'all'
• 'cursor'
• 'z-index'

• Elements which can be in different states keep this ability, and the relevant pseudo-classes match as usual.
• If a <{select}> element is activated, the UI to choose one of the associated <{option}> elements is shown (although it may look different).
• Event handlers attached to the element trigger as usual.

	input[type=checkbox] {
		appearance: none;
		all: unset;
		width: 1em;
		height: 1em;
		display: inline-block;
		background: red;
	}
	input[type=checkbox]:checked {
		border-radius: 50%;
		background: green;
	}
	

Form Control Specific Rules

Single-Line Text Input Controls

Appendix A. Acknowledgments

Appendix B. Changes

Changes from the 22 December 2017 Working Draft

• Added details about form control specific rendering rules

Changes from the 22 Sep 2015 First Public Working Draft

• The caret-animation property have been removed. It may be reintroduced later given sufficient evidence for use cases.
• The ''resize'' property now also applies to replaced elements representing images or videos, and to iframes.
• The string values and dual values of the text-overflow property were moved to this specification from level 3.
• Move directional focus navigation properties from level 3 to level 4
• Content from the now stable [[CSS-UI-3]] has been merged in.

Appendix C. Considerations for Security and Privacy

Does this specification deal with personally-identifiable information?

No.

Does this specification deal with high-value data?

No.

Does this specification introduce new state for an origin that persists across browsing sessions?

No.

Does this specification expose persistent, cross-origin state to the web?

No.

Does this specification expose any other data to an origin that it doesn’t currently have access to?

No.

Does this specification enable new script execution/loading mechanisms?

Yes to loading, but not to execution. The 'cursor' property accepts <> values which may include URLs to be loaded. These may be SVG documents which may contain scripts, but this specification requires that scripts must not be run.

Does this specification allow an origin access to a user’s location?

No.

Does this specification allow an origin access to sensors on a user’s device?

Yes. The directional focus navigation properties indirectly allow access to the device's keyboard navigation input mechanism such as arrow keys.

Does this specification allow an origin access to aspects of a user’s local computing environment?

No.

Does this specification allow an origin access to other devices?

No.

Does this specification allow an origin some measure of control over a user agent’s native UI?

Yes. The 'cursor' and 'caret' property and sub-properties enable the page to change the display of the cursor and text insertion caret of the user agent’s native UI. In addition the 'outline-style' property’s ''outline-style/auto'' value (and thus 'outline' shorthand) enable the page to potentially display a native focused element outline presentation around any element. The 'appearance' property also allows author to turn off native styling and replace it with css based styling.

Does this specification expose temporary identifiers to the web?

No.

Does this specification distinguish between behavior in first-party and third-party contexts?

No.

How should this specification work in the context of a user agent’s "incognito" mode?

No differently.

Does this specification persist data to a user’s local device?

No.

Does this specification have a "Security Considerations" and "Privacy Considerations" section?

Yes.

Does this specification allow downgrading default security characteristics?

No.

Appendix D. Default style sheet additions for HTML

This appendix is informative. Potential additions to the base style sheet to express HTML form controls, and a few dynamic presentation attributes:

:enabled:focus {
	outline: 2px inset;
}

button,
input[type=button],
input[type=reset],
input[type=submit],
input[type=checkbox],
input[type=radio],
textarea,
input,
input[type=text],
input[type=password],
input[type=image] {
	display: inline-block;
}

input[type=button],
input[type=reset],
input[type=submit],
input[type=checkbox],
input[type=radio],
input,
input[type=text],
input[type=password],
input[type=image] {
	white-space: nowrap;
}

button {
	/* white space handling of BUTTON tags in particular */
	white-space:normal;
}

input[type=reset]:lang(en) {
	/* default content of HTML input type=reset button, per language */
	content: "Reset";
}

input[type=submit]:lang(en) {
	/* default content of HTML input type=submit button, per language */
	content: "Submit";
}

/* UAs should use language-specific Reset/Submit rules for others. */

input[type=button],
input[type=reset][value],
input[type=submit][value] {
	/* text content/labels of HTML "input" buttons */
	content: attr(value);
}

textarea {
	/* white space handling of TEXTAREA tags in particular */
	white-space:pre-wrap;
	resize: both;
}

input[type=hidden] {
	/* appearance of the HTML hidden text field in particular */
	display: none !important;
}

input[type=image] {
	content: attr(src,url);
	border: none;
}

select[size] {
	/* HTML4/XHTML1 <select> w/ size more than 1 - appearance of list */
	display: inline-block;
	height: attr(size,em);
}

select,select[size=1] {
	/* HTML4/XHTML1 <select> without size, or size=1 - popup-menu */
	display: inline-block;
	height: 1em;
	overflow: hidden;
}

select[size]:active {
	/* active HTML <select> w/ size more than 1 - appearance of active list */
	display: inline-block;
}

optgroup, option {
	display: block;
	white-space: nowrap;
}

optgroup[label],option[label] {
	content: attr(label);
}

option[selected]::before {
	display: inline;
	content: check;
}

/* Though FRAME resizing is not directly addressed by this specification,
   the following rules may provide an approximation of reasonable behavior. */

/*

frame { resize:both }
frame[noresize] { resize:none }

*/