-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathOverview.bs
More file actions
1047 lines (860 loc) · 39 KB
/
Overview.bs
File metadata and controls
1047 lines (860 loc) · 39 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
7
8000
90
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<h1>CSS Basic User Interface Module Level 4</h1>
<pre class='metadata'>
ED: http://dev.w3.org/csswg/css-ui-4/
Status Text: This specification will include and extend <cite>CSS Basic User Interface Module Level 3.</cite> [[CSS3-UI]]
TR: http://www.w3.org/TR/css-ui-4/
Shortname: css-ui
Level: 4
Group: csswg
!Issue Tracking: https://wiki.csswg.org/spec/css4-ui#css4-ui-issues-list
Status: ED
Work Status: Exploring
Editor: Florian Rivoal, Invited Expert, florian@rivoal.net, http://florian.rivoal.net
Ignored Terms: box-sizing, resize, text-overflow, caret-color, nav-up, nav-down, nav-left, nav-right
Link Defaults: css-position-3 (property) position
Link Defaults: css21 (property) float
Link Defaults: css21 (property) clear
Link Defaults: selectors-4 (selector) :checked
Link Defaults: selectors-4 (selector) :enabled
Link Defaults: selectors-4 (selector) :disabled
Abstract: This specification describes user interface related
properties and values to style HTML and XML (including XHTML).
It includes and extends user interface related features
from the properties and values of previous CSS levels.
It uses various properties and values
to style basic user interface elements in a document.
</pre>
<h2 id="intro">Introduction</h2>
This module describes CSS properties which enable authors
to style user interface related properties and values.
<a href="http://www.w3.org/TR/REC-CSS1#anchor-pseudo-classes">Section 2.1 of CSS1</a> [[CSS1]]
and <a href="http://www.w3.org/TR/CSS2/ui.html">Chapter 18 of CSS2</a> [[CSS2]]
introduced several user interface related properties and values.
<a href="http://www.w3.org/TR/2000/WD-css3-userint-20000216">User Interface for CSS3 (16 February 2000)</a> introduced several new user interface related features.
[[CSS3-UI]] was later introduced to incorporates, extends, and supersedes these.
This specification continues this work, and in turn replaces [[CSS3-UI]].
Note: At the time of writing, [[CSS3-UI]] is not completely finalized yet.
To avoid accidental divergences and maintenance overhead,
This specification is written as a delta specification over CSS-UI Level 3.
Once the level 3 specification is final,
its content will be integrated into this specification,
which will then replace it.
Until then, CSS-UI Level 4 only contains additions and extensions to level 3.
<h3 id="purpose">Purpose</h3>
The purpose of this specification is to achieve the following objectives:
<ul>
<li>Extend the user interface features in CSS2.1 and [[CSS3-UI]]
<li>Provide additional CSS mechanisms to augment or replace other
dynamic presentation related features in HTML.
<li>Introduce directional navigation properties to assist in the construction of
user interfaces which make use of a directional navigation model.
</ul>
<h2 id="interaction">Module Interactions</h2>
This document defines new features not present in earlier specifications.
In addition, it replaces and supersedes [[!CSS3-UI]],
which itself replaced and superseded the following:
<ul>
<li><a href="http://www.w3.org/TR/CSS21/ui.html#cursor-props">Section 18.1</a>,
<a href="http://www.w3.org/TR/CSS21/ui.html#dynamic-outlines">section 18.4</a>,
and Information on the stacking of outlines defined in
<a href="http://www.w3.org/TR/CSS21/zindex.html">Appendix E</a>
of Cascading Style Sheets, level 2, revision 1 [[CSS21]]
<li><a href="http://www.w3.org/TR/2000/WD-css3-userint-20000216">User Interface for CSS3 (16 February 2000)</a> [[CSSUI]]
</ul>
<h2 id="box-model">Box Model addition</h2>
<h3 id="box-sizing">'box-sizing' property</h3>
Issue: Add final level 3 content
<h2 id="outline-props">Outline properties</h2>
Issue: Add final level 3 content
<h3 id="outline">'outline' property</h3>
Issue: Add final level 3 content
<h3 id="outline-width">'outline-width' property</h3>
Issue: Add final level 3 content
<h3 id="outline-style">'outline-style' property</h3>
Issue: Add final level 3 content
<h3 id="outline-color">'outline-color' property</h3>
Issue: Add final level 3 content
<h2 id="resizing-and-overflow">Resizing & Overflow</h2>
Issue: Add final level 3 content
<h3 id="resize">'resize' property</h3>
Issue: Add final level 3 content
<h3 id="text-overflow"> Overflow Ellipsis: the 'text-overflow' property</h3>
Issue: Add final level 3 content
This specification introduces a new value to the 'text-overflow' property:
''text-overflow/fade'', as well as its functional notation variant ''fade()''.
<pre class='partial propdef'>
Name: text-overflow
New values: ''fade'' | <<fade()>>
Computed value: As specified, with <<length>> converted to absolute units
</pre>
<dl dfn-type=value dfn-for=text-overflow>
<dt dfn-type=function><dfn>fade( <<length>> | <<percentage>> )</dfn></dt>
<dd>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 <<percentage>> 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?
<dt><dfn>fade</dfn></dt>
<dd>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.
</dl>
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?
<div class="example">
<style>
</style>
<table style="color:#000;background:#fff" id="awesome-table"><tbody>
<tr><th>HTML</th><th>sample rendering</th><th>your browser</th></tr>
<tr>
<td><pre><code class="lang-markup"><div style="<strong>text-overflow:fade;</strong> overflow:hidden">
CSS IS AWESOME, YES
</div>
</code></pre></td>
<td>
<object type="image/png" data="images/cssisfade.png">
a box with the text fading out on overflow.
</object></td>
<td>
<div style="width:3.1em; border:solid .1em black; padding:.2em; font-family:Helvetica,sans-serif; line-height:1.1; overflow:hidden;text-overflow:clip;">CSS IS AWESOME, YES</div>
</td>
</tr>
</table>
</div>
<h2 id="pointing-keyboard">Pointing Devices and Keyboards</h2>
<h3 id="pointer-interaction">Pointer interaction</h3>
<h4 id="cursor">'cursor' property</h4>
Issue: Add final level 3 content
Issue: Amend the definition of ''cursor/auto''
to show ''cursor/default'' rather than ''cursor/text''
over text when 'user-select' is ''user-select/none''.
<h3 id="insertion-caret">Insertion caret</h3>
<h4 id="caret-color">Coloring the insertion caret: 'caret-color'</h4>
Issue: Add final level 3 content
Issue: Amend the definition of ''caret-color/auto'' to highlight
the fact that when 'caret-shape' is ''caret-shape/block'',
ensuring good visibility and contrast means not using
currentColor.
<h4 id="caret-animation">Animation of the insertion caret: 'caret-animation'</h4>
<pre class='propdef'>
Name: caret-animation
Value: auto | blink | none | fade
Initial: auto
Applies to: elements that accept input
Inherited: yes
Percentages: N/A
Media: interactive
Computed value: Same as specified value.
Animatable: no
</pre>
On most platforms and in most UAs,
the text insertion caret blinks.
This property allows the author
to control the speed at which it blinks,
or to turn off blinking entirely.
<dl dfn-type=value dfn-for=caret-animation>
<dt><dfn>auto</dfn>
<dd>The UA determines how the caret should be animated, if at all.
It should match platform conventions,
and may be adjusted based on context.
Note: This is typically rendered as a blinking caret.
<dt><dfn>blink</dfn>
<dd>The UA must display a blinking caret.
For accessibility reasons, and based on user preferences,
The UA may display a non animated caret instead.
<dt><dfn>none</dfn>
<dd>The UA must not animate the caret.
Note: This is only about UA driven animations of the caret.
If CSS animations are used to animate the caret color,
these should still apply normally.
<dt><dfn>fade</dfn>
<dd>The UA must display a caret repeatedly fading in and out,
similarly to ''caret-animation/blink'' except it appears and
disappears progressively rather than suddenly.
For accessibility reasons, and based on user preferences,
The UA may display a non animated caret instead.
</dl>
Issue: Do we need the accessibility escape hatch on blink and fade?
Would it be enough instead to expect the UI to put
<code>caret-animation:fixed !important</code> in the
user stylesheet when it wants to prevent the caret
from blinking?
The UA determines the speed at which the cursor blinks or fades.
It should follow platform conventions and settings.
Note: It is recommended to stop the caret from blinking or fading
using ''caret-animation: none''
when applying custom animations using [[CSS3-ANIMATIONS]],
to prevent the blinking or fading and the css animation to interfere.
Note: See <a href="http://www.w3.org/TR/WCAG20/#seizure">Guideline 2.3: Seizures: Do not design content in a way that is known to cause seizures</a> [[WCAG20]].
<div class=example>
A user who is disturbed by or has adverse reactions to blinking or flashing visuals
may want to make all carets static and non-blinking,
regardless of platform defaults or author settings.
This can be accomplished by with the folliwing rule in the user stylesheet.
<pre><code class="lang-css">
/* prevent the caret from blinking/flashing */
:read-write { caret-animation: none !important; }
/* prevent changes of caret-color, including animations */
:read-write { caret-color:auto !important; }
</code></pre>
</div>
UAs that do not have an editable user stylesheet
should provide a setting to disable
<a href="http://www.w3.org/TR/WCAG20/#blinksdef">blinking</a>,
<a href="http://www.w3.org/TR/WCAG20/#flash-def">flashing</a>
and animated carets.
UAs that do have an editable user stylesheet may want to provide this setting as well.
See [[WCAG]] <a href="http://www.w3.org/TR/WCAG20/#time-limits-pause">Guideline 2.2</a>
and <a href="http://www.w3.org/TR/WCAG20/#seizure">Guideline 2.3</a>
for details.
<div class=example>
Normally, the caret blinks between on and off.
This makes it alternate between 2 colors.
<pre><code class="lang-css">
textarea {
caret-animation: none;
caret-color: blue;
animation: caret-alternate 2s step-end infinite;
}
@keyframes caret-alternate {
50% { caret-color: red; }
}
</code></pre>
The simulated rendering below illustrates how this would look.
<style>
@-webkit-keyframes caret-alternate { 50% { border-color: red; } }
@keyframes caret-alternate { 50% { border-color: red; } }
</style>
<div style="border:inset; background: white; width: 10em;">
Text area
with color-alternating caret<span style="border-right: 2px solid blue;animation: caret-alternate 2s step-end infinite;-webkit-animation: caret-alternate 2s step-end infinite;"></span>
</div>
</div>
<h4 id="caret-shape">Shape of the insertion caret: 'caret-shape'</h4>
<pre class='propdef'>
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
</pre>
This property allows authors to specify
the desired shape of the text insertion caret.
Within the context of this definition, <dfn>character</dfn> is
to be understood as <em>extended grapheme cluster</em>,
as defined in [[!UAX29]], and <dfn>visible character</dfn>
means a character with a non-zero advance measure.
<dl dfn-type=value dfn-for=caret-shape>
<dt><dfn>auto</dfn>
<dd>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 <em>insert</em> key on their keyboard,
it may show a ''caret-shape/bar'' caret in insert mode,
and a ''caret-shape/block'' caret in overtype mode.
<dt><dfn>bar</dfn>
<dd>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.
<dt><dfn>block</dfn>
<dd>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.
<dt><dfn>underscore</dfn>
<dd>The UA must render the text insertion caret
as a thin line <a>under</a> (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.
</dl>
The width of the ''caret-shape/block'' and ''caret-shape/underscore'' carets
should be the advance measure of the next visible character after the insertion point,
or ''1ch'' if there is no next visible character
or if this information is impractical to determine.
When determining the orientation and appearance of the caret,
UAs must take into account the <a>writing mode</a> [[!CSS-WRITING-MODES-3]]
and must apply transformations [[!CSS-TRANSFORMS-1]].
If the edited text is laid out out on a path,
for instance by using the SVG <{textPath}> element,
UAs should also account for this.
The stacking position of the caret is left undefined, within the following constraints:
<ul>
<li>The caret must not be obscured by the background of the element
<li>UAs must render ''caret-shape/block'' carets so that the
character it overlaps with is not obscured by the caret
</ul>
<div class=example>
This illustrates the typical appearance of the various caret shapes.
In each of the sample renderings below,
the insertion point is between the letters u and m.
<style>
@-webkit-keyframes caret-bar { 50% { outline-color: transparent; } }
@-webkit-keyframes caret-block { 50% { background: transparent; } }
@-webkit-keyframes caret-underscore { 50% { border-color: transparent; } }
@keyframes caret-bar { 50% { outline-color: transparent; } }
@keyframes caret-block { 50% { background: transparent; } }
@keyframes caret-underscore { 50% { border-color: transparent; } }
#caret-shape-e
8096
xample {
min-width: 25em;
}
#caret-shape-example,
#caret-shape-example td,
#caret-shape-example th {
border: solid 1px;
}
#caret-shape-example td+td {
background:white;
}
</style>
<table id="caret-shape-example">
<tr><th>'caret-shape'<th>Sample rendering
<tr><td>''bar''<td>Lorem ipsu<span style="outline: 1px solid black;animation: caret-bar 2s step-end infinite;-webkit-animation: caret-bar 2s step-end infinite;">​</span>m
<tr><td>''block''<td>Lorem ipsu<span style="background: #bbb; -webkit-animation: caret-block 2s step-end infinite;animation: caret-block 2s step-end infinite;">m</span>
<tr><td>''underscore''<td>Lorem ispu<span style="border-bottom: 2px solid black; -webkit-animation: caret-underscore 2s step-end infinite; animation: caret-underscore 2s step-end infinite;">m</span>
</table>
</div>
<div class=example>
''caret-shape/underscore'' or ''caret-shape/block'' carets are commonly used
in terminals and command lines,
as in this example.
<pre><code class="lang-css">
.console {
caret-shape: underscore;
background: black;
color: white;
font-family: monospace;
padding: 1ex;
}
</code></pre>
<style>
@-webkit-keyframes terminal-caret { 50% { border-color: transparent; } }
@keyframes terminal-caret { 50% { border-color: transparent; } }
</style>
<pre style="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 $ <span style="border-bottom: 2px solid white;animation: terminal-caret 2s step-end infinite;-webkit-animation: terminal-caret 2s step-end infinite;"> </span>
</pre>
</div>
<h4 id="caret">Insertion caret shorthand: 'caret'</h4>
<pre class='propdef'>
Name: caret
Value: <<'caret-color'>> || <<'caret-animation'>> || <<'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
</pre>
This property is a shorthand for setting
'caret-color', 'caret-animation' and 'caret-shape' in one declaration.
Omitted values are set to their initial values.
<div class=example>
This example illustrates using the various caret related properties
in combination.
They are used here to simulate the appearance of the caret
on an old phosphor computer monitor.
<pre><code class="lang-css">
#old-screen {
caret: block 0s;
animation: old-caret 2s infinite;
/*styling of the screen omitted for brevity */
}
@keyframes old-caret {
from, 50% { caret-color: green; }
75%, to { caret-color: transparent; }
}
</code></pre>
<style>
#old-screen {
border-radius: 1em;
padding: 1em;
color: green;
font-family: monospace;
background: repeating-linear-gradient(#030 0px, #030 1px, #020 1px, #020 3px);
}
#old-screen span {
display:inline-block;
white-space: pre;
caret: block 0s;
animation: caret-old 2s infinite;
-webkit-animation: caret-old 2s infinite;
}
@keyframes caret-old {
from, 50% { background-color: green; }
75%, to { background-color: transparent; }
}
@-webkit-keyframes caret-old {
from, 50% { background-color: green; }
75%, to { background-color: transparent; }
}
</style>
<div id="old-screen" style="height: 100px">> <span> </span></div>
</div>
<h3 id="keyboard">Keyboard control</h3>
<h4 id="nav-dir">Directional focus navigation: the 'nav-up', 'nav-right', 'nav-down', 'nav-left' properties</h4>
Issue: Add final level 3 content
<h4 id="input-method-editor">Obsolete: the ime-mode property</h4>
Issue: Add final level 3 content
<h2 id="user-interaction">User Interaction</h2>
<h3 id="content-selection">Controlling content selection</h3>
The 'user-select' property enables authors to specify
which elements in the document can be selected by the user and how.
This allows for easier interactions when not
all elements are equally useful to select,
avoiding accidental selections of neighbouring content.
<pre class='propdef'>
Name: user-select
Value: auto | text | none | contain | all
Initial: auto
Inherited: no
Applies to: all elements
Media: interactive
Computed value: See below
</pre>
User Agents must not apply the 'user-select' property to
the ''::first-line'' and ''::first-letter'' pseudo elements.
Issue: Whether 'user-select' should apply to ''::before'' and
''::after'' is an open question.
The computed value is the specified value,
except:
<ol>
<li>on <a>editable element</a>s
where the computed value is always ''user-select/contain''
regardless of the specified value
<li>when the specified value is ''user-select/auto'',
which computes one of the other values as defined below
</ol>
For the purpose of this specification,
an <dfn>editable element</dfn> is either
an <a href="https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#editing-host">editing host</a>
or a <a href="http://www.w3.org/TR/html/forms.html#mutability">mutable</a> form control with textual content,
such as <{textarea}>.
Issue: Should there be constraints
on what happens to the computed value
on elements that are editable descendants of editing hosts?
The semantics are not obvious.
Maybe ''user-select/none'' should compute to ''text'',
or maybe all values should compute to ''text''.
<dl dfn-type=value dfn-for=user-select>
<dt><dfn>auto</dfn>
<dd>The computed value of ''user-select/auto'' is determined as follows:
<ul>
<li>If the element is an <a>editable element</a>,
the computed value is ''contain''
<li>Otherwise,
if the computed value of 'user-select' on the parent of this element is ''all'',
the computed value is ''all''
<li>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''
<li>Otherwise, the computed value is ''text''
</ul>
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 ''contain'' value does not inherit.
<dt><dfn>text</dfn>
<dd>The element imposes no constraint on the selection.
<dt><dfn>none</dfn>
<dd>
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.
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.
<dt><dfn>contain</dfn>
<dd>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 ''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 <code>user-select: element</code>.
<dt><dfn>all</dfn>
<dd>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.
</dl>
Note: Selections can include more than just text and extend over images, tables, videos, etc.
The behavior when copying and pasting a such selections is out of scope for this specification.
The following additions are made to the UA stylesheet for HTML:
<pre><code class="lang-css">
button, meter, progress, select { user-select: none; }
</code></pre>
Issue: the list above is incomplete, and needs to include
at least the various button-like variants of <{input}>.
<h2 id="form-styling">Form Control Styling</h2>
<h3 id="appearance-switching">Switching appearance</h3>
While the way most elements in a document look can be fully controlled by CSS,
form controls are typically rendered by UAs using native UI controls of the host operating system,
which can neither be replicated nor styled using CSS.
This specification introduces the 'appearance' property
to provide some control over this behavior.
Using ''appearance: none'' allows authors
to suppress the native style of form controls,
so that CSS can be used to fully restyle them.
<pre class="propdef">
Name: appearance
Value: ''auto'' | ''none''
Initial: auto
Applies To: all elements
Inherited: no
Computed value: As specified
Media: all
</pre>
Issue: Should ''appearance/auto'' compute to ''appearance/none'' on regular elements?
I would say no:
If we did that,
to be consistent,
every time we introduced a new value,
we would change what ''appearance/auto'' computes to on some elements,
which doesn't sounds desirable.
Note: This specification intentionally refrains from making the appearance
of all possible form controls and sub-controls available as values,
as had previously been attempted by earlier proposals for this property
and by several UA vendors in experimental implementations.
Experience has shown that such a list would be very long and not practical to maintain,
and UAs would need to add non-standard values
to account for the behavior of non-standard pseudo-elements
sometimes used to implement form controls.
Moreover, many values of such an enumeration only make sense
on a single element or pseudo-element,
and are never used outside of the UA stylesheet.
Instead, this specification only provides
''appearance/auto'', ''appearance/none''.
UAs cannot therefore use the 'appearance' property
in the UA stylesheet to give each control is native look and feel,
and must use ''appearance:auto'' instead.
Issue: IE supports -webkit-appearance, and also includes the textfield and button values.
Presumably this was done due to compatibility problems,
so we may need to include it as well.
<dl dfn-type=value dfn-for=appearance>
<dt><dfn>auto</dfn>
<dd>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.
<dt><dfn>none</dfn>
<dd> 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.
From controls are <em>not</em> 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.
</dl>
On form control elements where the computed value is ''appearance/auto''
UAs may disregard some CSS properties
to ensure that the intended appearance is preserved,
or because these property may not be meaningful for the chosen appearance.
However, the following properties must not be disregarded:
<ul>
<li>'appearance'
<li>'display'
<li>'visibility'
<li>'position'
<li>'top'
<li>'right'
<li>'bottom'
<li>'left'
<li>'float'
<li>'clear'
</ul>
Issue: Are there more properties should include in this list?
Should we remove some?
Should whitelist the properties that are ok to ignore instead of
blacklisting those that are not?
Either way, UAs do ignore some properties when rendering form controls,
so this specification needs to say something about this.
All decorative visual aspects of a form control which are not caused by a CSS style rule
must be suppressed when the appearance is changed using 'appearance',
even if the UA's internal representation for this element
was composed of multiple elements or pseudo elements combined together.
For example, <{select}> is often rendered with an arrow on the right side
indicating that the list will be expanded if the element is clicked,
If the computed value of 'appearance' is ''appearance/none'', this
must disappear.
However, the UA must preserve aspects of the form control
which are necessary to operate the control with its original semantics.
This does not include aspects of a control which are merely needed to observe the state the control is in,
only those that are needed for the user to be able to modify the state of the control.
The UA may however give them a different look and feel
as long as it remains possible to operate the control.
For example,
the slider of an <code class="lang-markup"><input type=range></code> is preserved
(or replaced by an equivalent mechanism)
even if 'appearance' is ''appearance/none''
as it would otherwise not be possible to change the value of the range with the mouse or touchscreen.
On the other hand,
the check mark in an <code class="lang-markup"><input type=checkbox checked></code>
must be suppressed,
as it merely indicates the state the element is in,
which can be styled in different ways using the '':checked'' selector.
Issue: UAs are inconsistent about the preceding two paragraphs.
What is specified here attempts to give some logic
to what is preserved and what is not,
based on the use-cases for 'appearance'.
UAs should include in their User Agent stylesheet style rules
to give form controls a recognizable shape when 'appearance' is ''appearance/none''.
Note: Authors may therefore need to override these UA style rules to get the styling
they intended, possibly by using ''all: unset''.
Issue: This usage of the 'all' property would remove focus indicators
created by the 'outline' property,
which seems undesirable.
Using ''all: revert'' would not solve it, as it would fail to remove
the UA styles as intended.
How can we mitigate this?
The behavior and semantics of elements remain defined by the host language,
and are not influenced by this property.
For example, regardless of the computed value of 'appearance':
<ul>
<li>Elements which can be in different states keep this ability,
and the relevant pseudo-classes match as usual.
<li>If a <{select}> element is activated,
the UI to choose one of the associated <{option}> elements is shown
(although it may look different).
<li>Event handlers attached to the element trigger as usual.
</ul>
Conversely, changing the appearance of an element must not cause it
to acquire new semantics, pseudo classes, event handlers, etc
that it did not initially have.
The ability for an element to be focused
is also not changed by the 'appearance' property.
<div class=example>
An author wanting to customize the look and feel of check boxes in HTML could use the following:
<pre><code class="lang-css">
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;
}
</code></pre>
<code class="lang-markup"><input type="checkbox"></code> would be rendered as
<span style="display: inline-block; width: 1em; height: 1em; background: red;"></span>,
while <code class="lang-markup"><input type="checkbox" checked></code> would be rendered as
<span style="display: inline-block; width: 1em; height: 1em; background: green; border-radius: 50%;"></span>,
and activating (for example by clicking) the element would toggle the state as usual.
</div>
<hr title="Separator from footer">
<h2 class="no-num" id="acknowledgments">Appendix A. Acknowledgments</h2>
This appendix is <em>informative</em>.
This specification builds upon [[CSS3-UI]],
which was edited and written for the most part
by Tantek Çelik from 1999 to the present,
first while representing Microsoft, then as an invited expert,
and most recently while representing Mozilla.
Later work on level 3 and on this level 4
was done by Florian Rivoal,
working on behalf of Bloomberg.
Thanks to feedback and contributions from
<span class="h-card">Rossen Atanassov</span>,
<span class="h-card">Tab Atkins</span>,
<span class="h-card">L. David Baron</span>,
<span class="h-card">Bert Bos</span>,
<span class="h-card">Matthew Brealey</span>,
<span class="h-card">Rick Byers</span>,
<span class="h-card">Ada Chan</span>,
<span class="h-card">James Craig</span>,
<span class="h-card">Michael Cooper</span>,
<span class="h-card">Axel Dahmen</span>,
<span class="h-card">Michael Day</span>,
<span class="h-card">Micah Dubinko</span>,
<span class="h-card">Elika E.</span>,
<span class="h-card">Steve Falkenburg</span>,
<span class="h-card">Andrew Fedoniouk</span>,
<span class="h-card">Al Gilman</span>,
<span class="h-card">Ian Hickson</span>,
<span class="h-card">Bjoern Hoehrmann</span>,
<span class="h-card">Alan Hogan</span>,
<span class="h-card">David Hyatt</span>,
<span class="h-card">Richard Ishida</span>,
<span class="h-card">Sho Kuwamoto</span>,
<span class="h-card">Yves Lafon</span>,
<span class="h-card">Stuart Langridge</span>,
<span class="h-card">Susan Lesch</span>,
<span class="h-card">Peter Linss</span>,
<span class="h-card">Kang-Hao Lu</span>,
<span class="h-card">Masayuki Nakano</span>,
<span class="h-card">Mats Palmgren</span>,
<span class="h-card">Brad Pettit</span>,
<span class="h-card">François Remy</span>,
<span class="h-card">Andrey Rybka</span>,
<span class="h-card">Simon Sapin</span>,
<span class="h-card">Alexander Savenkov</span>,
<span class="h-card">Sebastian Schnitzenbaumer</span>,
<span class="h-card">Lea Verou</span>,
<span class="h-card">Etan Wexler</span>,
<span class="h-card">David Woolley</span>,
<span class="h-card">Frank Yan</span>,
<span class="h-card">Boris Zbarsky</span>,
and
<span class="h-card">Domel</span>.
<h2 class="no-num" id="changes">Appendix B. Changes</h2>
This appendix is <em>informative</em>.
This appendix describes functional changes from the Level 3
<a href="http://www.w3.org/TR/2015/CR-css-ui-3-20150707/"
>Candidate Recommendation (CR) of 7 Jul 2015</a>.
<ul>
<li>The 'user-select' property has been added
<li>The 'appearance' property has been added
<li>The ''text-overflow/fade'' and ''fade()'' values have been added to 'text-overflow'
<li>The 'caret' shorthand property and the 'caret-shape' and 'caret-animation' properties have been added.
</ul>
<h2 class="no-num" id="security-privacy-considerations">Appendix C. Considerations for Security and Privacy</h2>
This appendix is <em>informative</em>.
The W3C TAG is developing a
<a href="https://w3ctag.github.io/security-questionnaire/">Self-Review Questionnaire: Security and Privacy</a>
for editors of specifications to informatively answer.
Per the <a href="https://w3ctag.github.io/security-questionnaire/#questions">Questions to Consider</a>
<ol>
<li>Does this specification deal with personally-identifiable information?
<p>No.</p>
</li>
<li>Does this specification deal with high-value data?
<p>No.</p>
</li>
<li>Does this specification introduce new state for an origin that persists across browsing sessions?
<p>No.</p>
</li>
<li>Does this specification expose persistent, cross-origin state to the web?
<p>No.</p>
</li>
<li>Does this specification expose any other data to an origin that it doesn’t currently have access to?
<p>No.</p>
</li>
<li>Does this specification enable new script execution/loading mechanisms?
<p>No.</p>
</li>
<li>Does this specification allow an origin access to a user’s location?
<p>No.</p>