-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathOverview.html
More file actions
executable file
·4645 lines (3458 loc) · 156 KB
/
Overview.html
File metadata and controls
executable file
·4645 lines (3458 loc) · 156 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
790
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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html401/strict.dtd">
<!-- the command line to process is this is:
num -l 2 template.html | toc -l 2 | perl bin/htmlindex | perl \
bin/propindex | perl bin/addcite -r '' template.html \
>template-processed.html
To do: add longdesc
-->
<html>
<head><meta content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<meta content="text/css" http-equiv=Content-Style-Type>
<meta content=en http-equiv=Content-Language>
<meta content="Tantek Çelik" lang=tr name=author>
<title>CSS Basic User Interface Module Level 3 (CSS3 UI)</title>
<link href=default.css rel=stylesheet title=Default type="text/css">
<style type="text/css">
.subtoc ul,.subtoc ol { list-style-type: none }
ol.objectives { list-style: decimal }
ol.issues { list-style: decimal }
.html4ss { font-size:90%}
table.twod { border: solid 2px #777; font-family:sans-serif; font-size:9px }
table.twod td { border: solid 1px #777; font-family:sans-serif; font-size:9px }
table.twod th { font-size:10px; font-weight:bold }
h1 {font-size:200%; clear:both}
h2 {font-size:170%; clear:both}
h3 {font-size:150%; clear:both}
h4 {font-size:130%}
h5 {font-size:120%}
h6 {font-size:110%}
h1+h2 {page-break-before: avoid}
h2 {page-break-before: always}
dd p:first-child { margin-top:0 }
table.tprofile th.title {background:gray; color:white}
table.tprofile th { width:29%;padding:2px }
table.tprofile td { width:71%;padding:2px }
table#egappearance td:first-child { text-align:center; line-height:1.5 }
table#egappearance label { white-space:nowrap }
table#egappearance fieldset { line-height:1.4 }
table#egappearance legend { line-height:1.1 }
</style>
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel=stylesheet
type="text/css">
<body>
<div class=head> <a href="http://www.w3.org/"><img alt=W3C height=48
src="http://www.w3.org/Icons/w3c_home" width=72> </a>
<h1>CSS Basic User Interface Module Level 3</h1>
<h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 September
2010</h2>
<dl>
<dt>This version:</dt>
<!-- <dd><a href="http://www.w3.org/TR/2010/ED-css3-ui-20100928">http://www.w3.org/TR/2010/ED-css3-ui-20100928</a></dd> -->
<dd><a
href="http://dev.w3.org/csswg/css3-ui/">http://dev.w3.org/csswg/css3-ui/</a>
<dt>Latest version:
<dd><a
href="http://www.w3.org/TR/css3-ui">http://www.w3.org/TR/css3-ui</a>
<dt>Latest editor's draft:
<dd><a
href="http://dev.w3.org/csswg/css3-ui/">http://dev.w3.org/csswg/css3-ui/</a>
<dt>Previous version:
<dd><a
href="http://www.w3.org/TR/2004/CR-css3-ui-20040511/">http://www.w3.org/TR/2004/CR-css3-ui-20040511/</a>
<dt>Editor:
<dd class=vcard><span class=fn lang=tr>Tantek Çelik</span> (<a
class="company role url" href="http://tantek.com/">invited expert</a>,
and before at <a href="http://www.microsoft.com/">Microsoft
Corporation</a>) <<a class=email
href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>>
</dl>
<!--begin-copyright-->
<p class=copyright><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
rel=license>Copyright</a> © 2010 <a
href="http://www.w3.org/"><acronym title="World Wide Web
Consortium">W3C</acronym></a><sup>®</sup> (<a
href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute
of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym
title="European Research Consortium for Informatics and
Mathematics">ERCIM</acronym></a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
and <a
href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p>
<!--end-copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id=abstract>Abstract</h2>
<p>This section is <em>informative</em>.
<p>CSS (Cascading Style Sheets) is a language for describing the rendering
of HTML and XML documents on screen, on paper, in speech, etc. It uses
various selectors, properties and values to style basic user interface
elements in a document. This specification describes those user interface
related selectors, properties and values that are proposed for CSS
level 3 to style HTML and XML (including XHTML and XForms). It
includes and extends user interface related features from the selectors,
properties and values of CSS level 2 revision 1 and Selectors
specifications.
<h2 class="no-num no-toc" id=status style="page-break-before:auto">Status
of this document</h2>
<!--begin-status-->
<p>This is a public copy of the editors' draft. It is provided for
discussion only and may change at any moment. Its publication here does
not imply endorsement of its contents by W3C. Don't cite this document
other than as work in progress.
<p>The (<a
href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public
mailing list <a
href="mailto:www-style@w3.org?Subject=%5Bcss3-ui%5D%20PUT%20SUBJECT%20HERE">
www-style@w3.org</a> (see <a
href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for
discussion of this specification. When sending e-mail, please put the text
“css3-ui” in the subject, preferably like this:
“[<!---->css3-ui<!---->] <em>…summary of
comment…</em>”
<p>This document was produced by the <a href="/Style/CSS/members">CSS
Working Group</a> (part of the <a href="/Style/">Style Activity</a>).
<p>This document was produced by a group operating under the <a
href="/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent
Policy</a>. W3C maintains a <a href="/2004/01/pp-impl/32061/status"
rel=disclosure>public list of any patent disclosures</a> made in
connection with the deliverables of the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains <a
href="/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
W3C Patent Policy</a>.</p>
<!--end-status-->
<p>This specification is a <strong>Last Call Working Draft</strong>,
although it was previously a Candidate Recommendation. It has been
returned to Last Call Working Draft because this draft removes features
that were not implemented sufficiently to advance to Proposed
Recommendation, and had not been previously listed as at risk, as <a
href="http://www.w3.org/2005/10/Process-20051014/tr.html#cfi">required</a>
by the W3C Process.
<!-- This specification may advance directly to Proposed
Recommendation following the last call, depending on comments and
implementation reports. -->
All persons are encouraged to review this document and send comments to
the <a href="http://lists.w3.org/Archives/Public/www-style/">www-style
mailing list</a> as described above. The <strong>deadline for
comments</strong> is <strong>SOMETIME IN THE FUTURE AFTER A PUBLIC LCWD IS
PUBLISHED</strong>.
<h3 class="no-num no-toc" id=crec>Candidate Recommendation Exit Criteria</h3>
<p>For this specification to enter the Proposed Recommendation stage, the
following conditions shall be met:
<ol>
<li>
<p>There must be at least two interoperable implementations for every
feature. For the purposes of this criterion, we define the following
terms:</p>
<dl>
<dt>feature
<dd>
<p> A section or subsection of the specification.</p>
<dt>interoperable
<dd>
<p>passing the respective test cases in the test suite, or, if the
implementation is not a web browser, equivalent tests. Every relevant
test in the test suite should have an equivalent test created if such
a user agent (UA) is to be used to claim interoperability. In addition
if such a UA is to be used to claim interoperability, then there must
one or more additional UAs which can also pass those equivalent tests
in the same way for the purpose of interoperability. The equivalent
tests must be made publicly available for the purposes of peer review.</p>
<dt>implementation
<dd>
<p>a user agent which:</p>
<ol class=inline>
<li>implements the feature.
<li>is available (i.e. publicly downloadable or available through some
other public point of sale mechanism). This is the "show me"
requirement.
<li>is shipping (i.e. development, private or unofficial versions are
insufficient).
<li>is not experimental (i.e. is intended for a wide audience and
could be used on a daily basis).
</ol>
</dl>
<li>
<p>A minimum of six months of the CR period must have elapsed. This is to
ensure that enough time is given for any remaining major errors to be
caught.
<li>
<p>The CR period will be extended if implementations are slow to appear.
<li>
<p>Features that are <em>at risk</em> (see the below list) will be
dropped (thus reducing the list of "all" features mentioned above) if
two or more interoperable implementations of those features are not
found by the end of the CR period, or if sufficient and adequate tests
(by judgment of the Working Group) have not been produced for those
features by the end of the CR period.
</ol>
<p>A <a href="/Style/CSS/Test/">test suite</a> and a <a
href="/Style/css3-updates/css3-ui-implementations">report on
implementations</a> will be provided before the document becomes a
Proposed Recommendation.
<h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
<p>The Working Group has identified the following features as at risk of
being removed from CSS Basic User Interface Module Level 3 when exiting
CR. Implementors are urged to implement these features, if they wish to
see these features remain in this specification. All other features are
either defined in a normative reference (e.g. CSS 2.1 <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> or Selectors <a
href="#SELECT" rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>), or
dependencies for another specification (e.g. XForms <a href="#XFORMS10"
rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>) or are believed to have
one or more implementations (perhaps experimental), and thus will not be
dropped without returning to last call.
<ul><!-- Not at risk:
<li>CSS2.1: :hover :active :focus</li>
<li>Selectors: :enabled :disabled :checked :indeterminate ::selection</li>
<li>XForms needs: :default :valid :invalid :in-range :out-of-range :required :optional :read-only :read-write ::value ::choices ::repeat-item ::repeat-index</li>
<li>appearance:
Moz implements:
checkbox tab tooltip window dialog menubar
none(same as normal) button(same as push-buttom) radio(same as radio-button) menupopup(same as pop-up-menu) menuitem(same as menu-item)
checkboxcontainer(same as checkbox-group?) radiocontainer(same as radio-group?)
treeview(same as outline-tree?) textfield(same as field) menulist(sa
9E70
me as list-menu?) slider(same as range?) menulist(same as pull-down-menu?)
listbox? listitem?
hyperlink (with a different mechanism?)
XForms asked for and/or needs:
combo-box signature password
Required generic values:
icon button menu
Necessary to replace old CSS3 Color values, so they can be deprecated
document workspace desktop
</li>
<li>box-sizing implemented by IE5/Mac, Opera
-moz-box-sizing implemented by Mozilla
</li>
<li>outline, outline-width, outline-color, outline-style all in CSS 2.1</li>
<li>outline-offset property
implemented by Safari 1.2
</li>
<li>cursor property:
CSS2.1: auto | default | help | pointer | wait | crosshair | text |
e-resize | n-resize | ne-resize | nw-resize | s-resize | se-resize | sw-resize | w-resize
IE5/Mac implements: none | progress | cell
IE6/Windows implements: <uri> | progress | not-allowed | no-drop | vertical-text | all-scroll | col-resize | row-resize | move |
Mozilla implements: progress | cell(as -moz-cell) | alias(as -moz-alias) | copy(as -moz-copy) | context-menu(as -moz-context-menu) |
freedesktop.org copied all the cursors from the CSS3-UI LC Working Draft
by FredrikHoeglund - 14 Oct 2003
http://freedesktop.org/Standards/cursor-spec
</li>
<li>‘<code class=property>cursor</code>’ property values: ew-resize | ns-resize | nesw-resize | nwse-resize
implemented by Firefox and Safari
</li>
<li>pointer-events property:
implemented by Firefox 3.6 and later, Safari 4 and later, Opera v?
</li>
<li>nav-* properties
implemented by Opera, Tasman v1 internal implementation
required (depended on) by DVB-HTML, ATSC standards
</li>
<li>‘<code class=property>resize</code>’ property
implemented by Firefox 4 and Safari
</li>
-->
<li>‘<a href="#font"><code class=property>font</code></a>’
property values: window | document | workspace | desktop | tooltip |
dialog | button | push-button | hyperlink | radio-button | checkbox |
menu-item | tab | menubar | pull-down-menu | pop-up-menu | list-menu |
radio-group | checkbox-group | outline-tree | range | field | combo-box |
signature | password
<li>‘<a href="#content"><code
class=property>content</code></a>’ property value: icon
<li>‘<a href="#icon"><code class=property>icon</code></a>’
property
</ul>
<h2 class="no-num no-toc" id=summary>Overview</h2>
<p>This section is <em>informative</em>.
<p>This document is one of the "modules" for the upcoming CSS3
specification. It not only describes the user interface related properties
and values that already exist in <a
href="http://www.w3.org/TR/REC-CSS1">CSS1</a> <a href="#CSS1"
rel=biblioentry>[CSS1]<!--{{CSS1}}--></a> and <a
href="http://www.w3.org/TR/CSS21">CSS2.1</a> <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, but introduces new
properties and values for CSS3 as well. The Working Group doesn't expect
that all implementations of CSS3 will implement all properties or values.
Instead, there will probably be a small number of variants of CSS3,
so-called "profiles".
<p>This document is the result of the merging of relevant parts of the
following Recommendations and Working Drafts, and the addition of some new
features.
<ul>
<li>Cascading Style Sheets, level 2, revision 1 <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>
<li>User Interface for CSS3 (16 February 2000) [[CSSUI]]
</ul>
<p>This specification contains:
<ul>
<li>Pseudo-classes and pseudo-elements to style user interface states and
element fragments respectively.
<li>Additions to the user interface features in <a
href="http://www.w3.org/TR/CSS21">CSS2.1</a>.
<li>The ability to style the appearance of various standard form elements
in languages such as HTML/XHTML/XForms (and properties to augment or
replace some of the remaining stylistic attributes in HTML4/XHTML1).
<li>Directional focus navigation properties.
<li>A mechanism to allow the styling of elements as icons for
accessibility.
</ul>
<h2 class="no-num no-toc" id=contents>Table of contents</h2>
<!--begin-toc-->
<ul class=toc>
<li><a href="#intro"><span class=secno>1. </span>Introduction</a>
<ul class=toc>
<li><a href="#purpose"><span class=secno>1.1. </span>Purpose</a>
<li><a href="#scope"><span class=secno>1.2. </span>Scope</a>
</ul>
<li><a href="#conformance"><span class=secno>2. </span>Conformance</a>
<ul class=toc>
<li><a href="#definitions"><span class=secno>2.1. </span>Definitions</a>
<li><a href="#classes-of-products"><span class=secno>2.2. </span>Classes
of products</a>
<li><a href="#profiles"><span class=secno>2.3. </span>Profiles</a>
<li><a href="#extensions"><span class=secno>2.4. </span>Extensions</a>
</ul>
<li><a href="#dependencies-on-other-modules"><span class=secno>3.
</span>Dependencies on other modules</a>
<li><a href="#user-interface-selectors"><span class=secno>4. </span>User
Interface Selectors</a>
<ul class=toc>
<li><a href="#pseudo-classes"><span class=secno>4.1. </span>User
interface states: pseudo-classes</a>
<ul class=toc>
<li><a href="#active"><span class=secno>4.1.1. </span>:active
details</a>
<li><a href="#pseudo-default"><span class=secno>4.1.2.
</span>:default</a>
<li><a href="#pseudo-validity"><span class=secno>4.1.3.
</span><span>:valid</span> and <span>:invalid</span></a>
<li><a href="#pseudo-range"><span class=secno>4.1.4.
</span><span>:in-range</span> and <span>:out-of-range</span></a>
<li><a href="#pseudo-required-value"><span class=secno>4.1.5.
</span><span>:required</span> and <span>:optional</span></a>
<li><a href="#pseudo-ro-rw"><span class=secno>4.1.6.
</span><span>:read-only</span> and <span>:read-write</span></a>
</ul>
<li><a href="#pseudo-elements"><span class=secno>4.2. </span>User
interface element fragments: pseudo-elements</a>
<ul class=toc>
<li><a href="#pseudo-value"><span class=secno>4.2.1.
</span>::value</a>
<li><a href="#pseudo-choices"><span class=secno>4.2.2.
</span>::choices</a>
<li><a href="#pseudo-repeat-item"><span class=secno>4.2.3.
</span>::repeat-item</a>
<li><a href="#pseudo-repeat-index"><span class=secno>4.2.4.
</span>::repeat-index</a>
</ul>
</ul>
<li><a href="#system-appearance"><span class=secno>5. </span>System
Appearance</a>
<ul class=toc>
<li><a href="#appearance-val"><span class=secno>5.1. </span>Appearance
values</a>
<li><a href="#appearance"><span class=secno>5.2. </span><span
class=property>‘<code
class=property>appearance</code>’</span> property</a>
<li><a href="#system-fonts"><span class=secno>5.3. </span>System
fonts</a>
</ul>
<li><a href="#element-icons"><span class=secno>6. </span>Element icons</a>
<ul class=toc>
<li><a href="#content-property-addition"><span class=secno>6.1.
</span><span class=property>‘<code
class=property>content</code>’</span> property addition</a>
<li><a href="#icon-property"><span class=secno>6.2. </span><span
class=property>‘<code class=property>icon</code>’</span>
property</a>
</ul>
<li><a href="#box-model-addition"><span class=secno>7. </span>Box Model
addition</a>
<ul class=toc>
<li><a href="#box-sizing"><span class=secno>7.1. </span><span
class=property>‘<code
class=property>box-sizing</code>’</span> property</a>
</ul>
<li><a href="#outline-properties"><span class=secno>8. </span>Outline
properties</a>
<ul class=toc>
<li><a href="#outline"><span class=secno>8.1. </span><span
class=property>‘<code class=property>outline</code>’</span>
property</a>
<li><a href="#outline-width"><span class=secno>8.2. </span><span
class=property>‘<code
class=property>outline-width</code>’</span> property</a>
<li><a href="#outline-style"><span class=secno>8.3. </span><span
class=property>‘<code
class=property>outline-style</code>’</span> property</a>
<li><a href="#outline-color"><span class=secno>8.4. </span><span
class=property>‘<code
class=property>outline-color</code>’</span> property</a>
<li><a href="#outline-offset"><span class=secno>8.5. </span><span
class=property>‘<code
class=property>outline-offset</code>’</span> property</a>
</ul>
<li><a href="#resizing"><span class=secno>9. </span>Resizing</a>
<ul class=toc>
<li><a href="#resize"><span class=secno>9.1. </span><span
class=property>‘<code class=property>resize</code>’</span>
property</a>
</ul>
<li><a href="#pointing-devices-and-keyboards"><span class=secno>10.
</span>Pointing Devices and Keyboards</a>
<ul class=toc>
<li><a href="#pointer-interaction"><span class=secno>10.1.
</span>Pointer interaction</a>
<ul class=toc>
<li><a href="#cursor"><span class=secno>10.1.1. </span><span
class=property>‘<code
class=property>cursor</code>’</span> property</a>
<li><a href="#pointer-events"><span class=secno>10.1.2. </span><span
class=property>‘<code
class=property>pointer-events</code>’</span> property</a>
</ul>
<li><a href="#keyboard"><span class=secno>10.2. </span>Keyboard
control</a>
<ul class=toc>
<li><a href="#nav-index"><span class=secno>10.2.1. </span>Sequential
navigation order: the <span class=property>‘<code
class=property>nav-index</code>’</span> property</a>
<li><a href="#nav-dir"><span class=secno>10.2.2. </span>Directional
focus navigation: the <span class=property>‘<code
class=property>nav-up</code>’</span>, <span
class=property>‘<code
class=property>nav-right</code>’</span>, <span
class=property>‘<code
class=property>nav-down</code>’</span>, <span
class=property>‘<code
class=property>nav-left</code>’</span> properties</a>
</ul>
</ul>
<li class=no-num><a href="#acknowledgments">Appendix A.
Acknowledgments</a>
<li class=no-num><a href="#references">Appendix B. Bibiliography</a>
<li class=no-num><a href="#changes">Appendix C. Changes</a>
<ul class=toc>
<li class=no-num><a href="#changes-list">List of specific changes</a>
</ul>
<li class=no-num><a
href="#appendix-d.-default-style-sheet-addition">Appendix D. Default
style sheet additions for HTML4/XHTML1</a>
<li class=no-num><a href="#appendix-e.-example-profiles">Appendix E.
Example profiles</a>
<li class=no-num><a href="#appendix-f-test-suite">Appendix F: Test
Suite</a>
<li class=no-num><a href="#index">Index</a>
<li class=no-num><a href="#property-index">Property index</a>
</ul>
<!--end-toc-->
<hr>
<h2 id=intro><span class=secno>1. </span>Introduction</h2>
<p>This section is <em>normative</em>.
<p> CSS3 is a set of modules, divided up and profiled in order to simplify
the specification, and to allow implementors the flexibility of supporting
the particular modules appropriate for their implementations.
<p> This module describes selectors and CSS properties which enable authors
to style user interface related states, element fragments, properties and
values.
<p><a href="http://www.w3.org/TR/REC-CSS1#anchor-pseudo-classes">Section
2.1 of CSS1</a> <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a>
and <a href="http://www.w3.org/TR/CSS2/ui.html">Chapter 18 of CSS2</a> <a
href="#CSS2" rel=biblioentry>[CSS2]<!--{{CSS2}}--></a> introduced several
user interface related pseudo-classes, properties and values. <a
href="http://www.w3.org/TR/css3-selectors/#UIstates">Section 6.6.4 of
Selectors</a> <a href="#SELECT"
rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a> also describes several
additional user interface related pseudo-classes (and one pseudo-element).
<p> This Working Draft extends them to provide the ability, through CSS, to
style elements based upon additional user interface states, to style
fragments of user interface elements, and to alter the dynamic
presentation of elements in ways previously only available through
specific HTML4/XHTML1 elements and attributes.
<h3 id=purpose><span class=secno>1.1. </span>Purpose</h3>
<p>The purpose of this specification is to achieve the following
objectives:
<ul>
<li>Extend the user interface features in CSS2.1.
<li>Provide additional CSS mechanisms to simulate the appearance of
various standard form elements.
<li>Provide additional CSS mechanisms to augment or replace other dynamic
presentation related features in HTML4/XHTML1.
<li>Introduce directional navigation properties to assist in the
construction of user interfaces which make use of a directional
navigation model.
<li>Introduce properties and values to specify icon presentations for
elements to enhance accessibility.
</ul>
<h3 id=scope><span class=secno>1.2. </span>Scope</h3>
<p>This proposal specifies how to alter the look and feel of various
elements, and specifically does not address the meaning behind what a
specific look and feel may imply. For example, with the additions in the
proposal, an author can make any element look and even feel like a submit
button. Yet, that arbitrary element is not afforded any additional
meaning, so pushing it does nothing by default, and certainly does not
submit a form.
<p> Similarly, the HTML4 <code><SELECT></code> element for example,
provides a list or menu of choices to the user. The meaning of the HTML4
<code><SELECT></code> element is that it allows the user to make a
choice, to choose something among several alternatives. This says nothing
about its look and feel, and in fact, the "concept" of a HTML4
<code><SELECT></code> could be visually implemented as a list-box, a
popup-menu, or a group of radio-buttons. Or a group of HTML4 checkboxes
(<code><INPUT type="checkbox"></code>) could be styled to appear as
a group of radio-buttons, and yet, since those elements are still semantic
checkboxes, they can still be individually checked or unchecked, rather
than acquiring any kind of radio-button group semantic where only one can
be checked.
<p> Each example of presentation has a different look and feel, but
maintains its original meaning, a choice (or choices) among several
alternatives. This proposal addresses only the former (look and feel), not
the latter (meaning).
<p> Since this proposal serves to simulate the appearance of various user
interface and forms elements in HTML4/XHTML, it is perhaps useful to call
out what specifically is believed to be outside the scope of CSS, or
better suited to document structure rather than style and therefore not
addressed by this proposal:
<ul>
<li>Form semantics, including, but not limited to, submission, resetting,
naming, what determines a successful or valid form control, and how to
process form data.
<li>Form contents, including, but not limited to initial value, current
value, and form content types. The HTML4 ‘<code
class=css><code>maxlength</code></code>’ attribute, for example,
determines the maximum number of characters the user can enter into an
<code><INPUT type="text"></code> or <code><INPUT
type="password"></code> field, and as such is a content constraint
rather than a presentational suggestion.
<li>Form control dependencies, including, but not limited to, whether only
one option from a set of choices may be chosen, or whether multiple
options may be chosen.
<li>The HTML4/XHTML1 <code><form></code> element and its unique
attributes (‘<code class=css><code>action</code></code>’,
‘<code class=css><code>method</code></code>’, ‘<code
class=css><code>enctype</code></code>’, ‘<code
class=css><code>accept</code></code>’, ‘<code
class=css><code>accept-charset</code></code>’).
</ul>
<p>In addition, this document does not attempt to solve all user interface
related issues / features that can be found in modern user interfaces.
Perhaps future versions may attempt to solve these. For example:
<ul>
<li>Complex or composite controls (e.g. the HTML4 <code><INPUT
type="file"></code> and the <code><ISINDEX></code> elements).
<li>The appearance, styling and coloring of scrollbars.
<li>Window layering. There is no attempt made to distinguish the
appearance of elements in the front-most window versus non-front-most
windows. The semantics of window layering must be addressed before it is
appropriate to attempt to style such concepts.
<li>Palettes and floating windows. Along with the concept of "frontmost"
window, windows that float but do not receive focus are also not
addressed.
<li>Browser window chrome and toolbars.
<li>The default styling of the HTML4/XHTML1 <code><fieldset></code>,
<code><legend></code>, <code><frame></code> and
<code><frameset></code> elements.
<li>Frame-resizing behavior. The behavior of <code><frame></code>
and <code><frameset></code>, specifically the ability to "share"
resizability when elements share a border, perhaps by leveraging the
border-collapse property is also not addressed.
</ul>
<h2 id=conformance><span class=secno>2. </span>Conformance</h2>
<p>This section is <em>normative</em>.
<h3 id=definitions><span class=secno>2.1. </span>Definitions</h3>
<p>The key words <span class=index-def id=must title=MUST>"MUST"</span>,
<span class=index-def id=must-not title="MUST NOT">"MUST NOT"</span>,
<span class=index-def id=required title=REQUIRED>"REQUIRED"</span>, <span
class=index-def id=shall title=SHALL>"SHALL"</span>, <span class=index-def
id=shall-not title="SHALL NOT">"SHALL NOT"</span>, <span class=index-def
id=should title=SHOULD>"SHOULD"</span>, <span class=index-def
id=should-not title="SHOULD NOT">"SHOULD NOT"</span>, <span
class=index-def id=recommended title=RECOMMENDED>"RECOMMENDED"</span>,
<span class=index-def id=may title=MAY>"MAY"</span>, and <span
class=index-def id=optional title=OPTIONAL>"OPTIONAL"</span> in this
document are to be interpreted as described in RFC 2119 (see <a
href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>).
However, for readability, these words do not typically appear in all
uppercase letters in this specification.
<p>Additional key words, e.g. "User agent (UA)", are <a
href="http://www.w3.org/TR/CSS21/conform.html#q1">defined by CSS 2.1</a>
(<a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, section
3.1).
<h3 id=classes-of-products><span class=secno>2.2. </span>Classes of
products</h3>
<p>The following classes of products (many of which overlap) should
consider implementing this specification:
<ul>
<li>Web browsers
<li>User agents that implement one or more of the following types of
content: HTML (e.g. <a href="#HTML401"
rel=biblioentry>[HTML401]<!--{{HTML401}}--></a>), XHTML (e.g. <a
href="#XHTML10" rel=biblioentry>[XHTML10]<!--{{XHTML10}}--></a>, <a
href="#XHTML11" rel=biblioentry>[XHTML11]<!--{{XHTML11}}--></a>), XForms
(e.g. <a href="#XFORMS10"
rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>), SVG (e.g. <a
href="#SVG10" rel=biblioentry>[SVG10]<!--{{SVG10}}--></a>, <a
href="#SVG11" rel=biblioentry>[SVG11]<!--{{SVG11}}--></a>) or other
content languages that contain forms controls or are intended for user
interaction
<li>User agents that implement one or more levels, modules and or profiles
of CSS (e.g. <a href="#CSS1" rel=biblioentry>[CSS1]<!--{{CSS1}}--></a>,
<a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>)
</ul>
<h3 id=profiles><span class=secno>2.3. </span>Profiles</h3>
<p>This specification contains a number of informative profiles. These
profiles are not mandatory for conformance.
<h3 id=extensions><span class=secno>2.4. </span>Extensions</h3>
<p>This specification does not define any explicit extension mechanisms. If
an implementation needs to extend the functionality of this specification,
it must follow any/all guidelines and requirements of extensions as
defined in CSS2.1, e.g. <a
href="http://www.w3.org/TR/CSS21/syndata.html#q4">Vendor-specific
extensions</a> (<a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, section 4.1.2).
<h2 id=dependencies-on-other-modules><span class=secno>3.
</span>Dependencies on other modules</h2>
<p>This section is <em>normative</em>.
<p>This CSS3 module depends on the following other specifications. Some of
these specifications may be in their "Candidate Recommendation" phase. If
this module depends on feature or portion of such a specification which
ends up being dropped during their "CR" phase(s), then such feature or
portion thereof will be presumed to be incorporated into this
specification. For example, if the ":indeterminate" selector was dropped
from Selectors, then the definition and description of ":indeterminate"
would be incorporated into the next draft of this specification.
<ul>
<li><a href="#SELECT" rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>
<li><a href="#CSS3COLOR"
rel=biblioentry>[CSS3COLOR]<!--{{!CSS3COLOR}}--></a>
<li><a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>
</ul>
<!--
<p>It has non-normative (informative) references to the following
other specifications:</p>
<ul>
</ul>
-->
<p> The following work is related to the CSS Basic User Interface Module
Level 3 (CSS3 Basic UI).
<ul>
<li><a href="#HTML401" rel=biblioentry>[HTML401]<!--{{HTML401}}--></a>
<li><a href="#UAAG10" rel=biblioentry>[UAAG10]<!--{{UAAG10}}--></a>
<li><a href="#XML10" rel=biblioentry>[XML10]<!--{{XML10}}--></a>
<li><a href="#XHTML10" rel=biblioentry>[XHTML10]<!--{{XHTML10}}--></a>
<li><a href="#XHTML11" rel=biblioentry>[XHTML11]<!--{{XHTML11}}--></a>
<li><a href="#XFORMS10" rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>
</ul>
<p>This specification does not define what is a form element.
<h2 id=user-interface-selectors><span class=secno>4. </span>User Interface
Selectors</h2>
<p>This section is <em>normative</em>.
<h3 id=pseudo-classes><span class=secno>4.1. </span>User interface states:
pseudo-classes</h3>
<p>The Selectors specification <a
href="http://www.w3.org/TR/css3-selectors/#UIstates">defines several user
interface selectors</a> (<a href="#SELECT"
rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>, sections 6.6.1 and 6.6.4)
which represent user interface states:
<ul>
<li id=psuedo-hover><a
href="http://www.w3.org/TR/css3-selectors/#useraction-pseudos">:hover</a>
<li id=pseudo-active><a
href="http://www.w3.org/TR/css3-selectors/#useraction-pseudos">:active</a>
<li id=pseudo-focus><a
href="http://www.w3.org/TR/css3-selectors/#useraction-pseudos">:focus</a>
<li id=pseudo-enabled><a
href="http://www.w3.org/TR/css3-selectors/#enableddisabled">:enabled</a>
<li id=pseudo-disabled><a
href="http://www.w3.org/TR/css3-selectors/#enableddisabled">:disabled</a>
<li id=pseudo-checked><a
href="http://www.w3.org/TR/css3-selectors/#checked">:checked</a>
<li id=pseudo-indeterminate><a
href="http://www.w3.org/TR/css3-selectors/#indeterminate">:indeterminate</a>
</ul>
<p>These pseudo-classes as defined by <a href="#SELECT"
rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a> are included in this
specification by reference.
<p>CSS 2.1 <a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>
specifies additional details for some of the selectors mentioned, above
and beyond Selectors.
<h4 id=active><span class=secno>4.1.1. </span>:active details</h4>
<p>In addition, on systems with more than one mouse button, :active is
clarified to apply only to the primary or primary activation button
(typically the "left" mouse button), and any aliases thereof.
<div class=example>
<p style="display:none">Example(s):</p>
<h4 class="no-num no-toc" id=restyling-a-checkbox>restyling a checkbox</h4>
<p> Authors may wish to completely redo the styling of a form control,
such as a checkbox. This can be achieved using several of the above
pseudo-classes and the ‘<code class=css><span
class=value>normal</span></code>’ value for the <span
class=property>‘<a href="#appearance0"><code
class=property>appearance</code></a>’</span> property which is
explained later in this specification. In this example, checkboxes with a
class of "redone" are styled with specific background images according to
their respective user interface states using one or more pseudo-classes.</p>
<pre><code class=css>
input[type=checkbox] {
appearance:checkbox; /* expected from UA defaults */
}
input[type=checkbox].redone {
appearance:normal; /* resets various properties */
display:inline-block;
width:20px; height:20px;
background:url(customuncheckedimage.png);
}
input[type=checkbox].redone:active {
background:url(customuncheckedactiveimage.png);
}
input[type=checkbox].redone:checked {
background:url(customcheckedimage.png);
}
input[type=checkbox].redone:checked:active {
background:url(customcheckedactiveimage.png);
}
input[type=checkbox].redone:disabled {
background:url(customdisableduncheckedimage.png);
}
input[type=checkbox].redone:disabled:checked {
background:url(customdisabledcheckedimage.png);
}
</code></pre>
</div>
<h4 class="no-num no-toc" id=new-user-interface-state-pseudo-classes>New
user interface state pseudo-classes</h4>
<p>In addition to the above-mentioned pseudo-classes, this specification
introduces several new pseudo-classes to define additional user interface
states.
<ul>
<li>:default
<li>:valid
<li>:invalid
<li>:in-range
<li>:out-of-range
<li>:required
<li>:optional
<li>:read-only
<li>:read-write
</ul>
<p>Specifically, these new states (except for :default) are provided as a
way to style elements which are in the respective states as defined by
XForms <a href="#XFORMS10"
rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>.
<h4 id=pseudo-default><span class=secno>4.1.2. </span>:default</h4>
<p>The :default selector applies to the one or more UI elements that are
the default among a set of similar elements. Typically applies to context
menu items, buttons and select lists/menus.
<p> One example is the default submit button among a set of buttons.
Another example is the default option from a popup menu. Multiple elements
in a select-many group could have multiple :default elements, like a
selection of pizza toppings for example.
<h4 id=pseudo-validity><span class=secno>4.1.3. </span><span
id=pseudo-valid>:valid</span> and <span id=pseudo-invalid>:invalid</span></h4>
<p>An element is :valid or :invalid when it is, respectively, valid or
invalid with respect to data validity semantics defined by a different
specification (e.g. <a href="#XFORMS10"
rel=biblioentry>[XFORMS10]<!--{{XFORMS10}}--></a>). An element which lacks
data validity semantics is neither :valid nor :invalid. This is different
from an element which otherwise has no constraints. Such an element would
always be :valid.
<h4 id=pseudo-range><span class=secno>4.1.4. </span><span
id=pseudo-in-range>:in-range</span> and <span
id=pseudo-out-of-range>:out-of-range</span></h4>
<p> The :in-range and :out-of-range pseudo-classes apply only to elements
that have range limitations. An element is :in-range or :out-of-range when
the value that the element is bound to is in range or out of range of the
presentation (e.g. visual or spoken representation) of the element
respectively. An element that lacks data range limits or is not a form
control is neither :in-range nor :out-of-range. E.g. a slider element with
a value of 11 presented as a slider control that only represents the
values from 1-10 is :out-of-range. Another example is a menu element with
a value of "E" that happens to be presented as a popup menu that only has
choices "A", "B" and "C".
<h4 id=pseudo-required-value><span class=secno>4.1.5. </span><span
id=pseudo-required>:required</span> and <span
id=pseudo-optional>:optional</span></h4>
<p>A form element is :required or :optional if a value for it is,
You can’t perform that action at this time.