forked from emumanu/OpenUI5Sharp
-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathsap.ui.core.xsd
More file actions
1662 lines (1624 loc) · 81.3 KB
/
sap.ui.core.xsd
File metadata and controls
1662 lines (1624 loc) · 81.3 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
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:n0="sap.ui.core" xmlns:n1="sap.ui.core.dnd" elementFormDefault="qualified" targetNamespace="sap.ui.core" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="sap.ui.core.dnd" />
<xs:element name="FragmentDefinition">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="n0:Control" />
<xs:element ref="n0:Fragment" />
<xs:any namespace="http://www.w3.org/1999/xhtml" processContents="lax" />
</xs:choice>
</xs:complexType>
</xs:element>
<xs:complexType name="_FragmentType0">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="id" type="n0:_IDType" />
<xs:attribute name="fragmentName" type="xs:string" />
<xs:attribute name="type" type="xs:string" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:element name="Fragment">
<xs:complexType>
<xs:simpleContent>
<xs:restriction base="n0:_FragmentType0">
<xs:enumeration value="" />
<xs:whiteSpace value="collapse" />
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ComponentContainer" substitutionGroup="n0:Control" type="n0:_ComponentContainerType">
<xs:annotation>
<xs:documentation>Container that embeds a UIComponent in a control tree.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ComponentContainerType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="name" type="xs:string">
<xs:annotation>
<xs:documentation>Component name, the package where the component is contained. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="url" type="n0:_URIType">
<xs:annotation>
<xs:documentation>The URL of the component. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="async" type="xs:boolean">
<xs:annotation>
<xs:documentation>Flag whether the component should be created sync (default) or async. The default will be async when initially the property <code>manifest</code> is set to a truthy value and for the property <code>async</code> no value has been specified. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="handleValidation" type="xs:boolean">
<xs:annotation>
<xs:documentation>Enable/disable validation handling by MessageManager for this component. The resulting Messages will be propagated to the controls. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="settings" type="xs:string">
<xs:annotation>
<xs:documentation>The settings object passed to the component when created. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="propagateModel" type="xs:boolean">
<xs:annotation>
<xs:documentation>Defines whether binding information is propagated to the component.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="width" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>Container width in CSS size</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="height" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>Container height in CSS size</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="lifecycle" type="n0:_ComponentLifecycleType">
<xs:annotation>
<xs:documentation>Lifecycle behavior for the Component associated by the <code>ComponentContainer</code>. The default behavior is <code>Legacy</code>. This means that the <code>ComponentContainer</code> takes care that the Component is destroyed when the <code>ComponentContainer</code> is destroyed, but it is <b>not</b> destroyed when a new Component is associated. If you use the <code>usage</code> property to create the Component, the default behavior is <code>Container</code>. This means that the Component is destroyed when the <code>ComponentContainer</code> is destroyed or a new Component is associated. This property must only be applied before a component instance is created.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="autoPrefixId" type="xs:boolean">
<xs:annotation>
<xs:documentation>Flag, whether to auto-prefix the ID of the nested Component or not. If this property is set to true the ID of the Component will be prefixed with the ID of the ComponentContainer followed by a single dash. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="usage" type="xs:string">
<xs:annotation>
<xs:documentation>The component usage. If the ComponentContainer is used inside a Component, this Component can define a usage which will be used for creating the Component. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="manifest" type="xs:string">
<xs:annotation>
<xs:documentation>Controls when and from where to load the manifest for the Component. When set to any truthy value, the manifest will be loaded asynchronously by default and evaluated before the Component controller, if it is set to a falsy value other than <code>undefined</code>, the manifest will be loaded after the controller. A non-empty string value will be interpreted as the URL location from where to load the manifest. A non-null object value will be interpreted as manifest content. This property can only be applied initially.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="component" type="xs:string">
<xs:annotation>
<xs:documentation>The component displayed in this ComponentContainer.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="componentCreated" type="xs:string">
<xs:annotation>
<xs:documentation>Fired when the component instance has been created by the ComponentContainer.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="Control" substitutionGroup="n0:Element" type="n0:_ControlType">
<xs:annotation>
<xs:documentation>Base Class for Controls.
Controls provide the following features: <ul> <li><b>Rendering</b>: the <code>RenderManager</code> only expects instances of class <code>Control</code> in its {@link sap.ui.core.RenderManager#renderControl renderControl} method. By convention, each control class has an associated static class that takes care of rendering the control (its 'Renderer').</li> <li><b>show / hide</b>: a control can be hidden, although it is still part of the control tree, see property {@link #getVisible visible}</li> <li><b>local busy indicator</b>: marks a control visually as 'busy', see properties {@link #getBusy busy} and {@link #getBusyIndicatorDelay busyIndicatorDelay}</li> <li><b>field groups</b>: by assigning the same group ID to a set of editable controls, they form a group which can be validated together. See property {@link #getFieldGroupIds fieldGroupIds} and event {@link #event:validateFieldGroup validateFieldGroup}. The term <i>field</i> was chosen as most often this feature will be used to group editable fields in a form.</li> <li><b>custom style classes</b>: all controls allow to add custom CSS classes to their rendered DOM without modifying their renderer code. See methods {@link #addStyleClass addStyleClass}, {@link #removeStyleClass removeStyleClass}, {@link #toggleStyleClass toggleStyleClass} and {@link #hasStyleClass hasStyleClass}.</br> The necessary implementation is encapsulated in {@link sap.ui.core.CustomStyleClassSupport CustomStyleClassSupport} and can be applied to selected element classes as well.</li> <li><b>browser events</b>: by calling the methods {@link #attachBrowserEvent attachBrowserEvent} and {@link #detachBrowserEvent detachBrowserEvent}, consumers can let the control class take care of registering / de-registering a given set of event listeners to the control's root DOM node. The framework will adapt the registration whenever the DOM node changes (e.g. before or after rendering or when the control is destroyed).</li> </ul>
See section "{@link topic:91f1703b6f4d1014b6dd926db0e91070 Developing OpenUI5/SAPUI5 Controls}" in the documentation for an introduction to control development.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ControlType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType">
<xs:attribute name="blocked" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether the control is currently in blocked state.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="busy" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether the control is currently in busy state.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="busyIndicatorDelay" type="xs:int">
<xs:annotation>
<xs:documentation>The delay in milliseconds, after which the busy indicator will show up for this control.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="busyIndicatorSize" type="n0:_BusyIndicatorSizeType">
<xs:annotation>
<xs:documentation>The size of the BusyIndicator. For controls with a width smaller 3rem a <code>sap.ui.core.BusyIndicatorSize.Small</code> should be used. If the size could vary in width and the width could get smaller than 3rem, the <code>sap.ui.core.BusyIndicatorSize.Auto</code> option could be used. The default is set to <code>sap.ui.core.BusyIndicatorSize.Medium</code> For a full screen BusyIndicator use <code>sap.ui.core.BusyIndicatorSize.Large</code>.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="visible" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether the control should be visible on the screen.
If set to false, a placeholder will be rendered to mark the location of the invisible control in the DOM of the current page. The placeholder will be hidden and have zero dimensions (<code>display: none</code>).
See {@link sap.ui.core.RenderManager#writeInvisiblePlaceholderData RenderManager#writeInvisiblePlaceholderData} for details.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="fieldGroupIds" type="xs:string">
<xs:annotation>
<xs:documentation>The IDs of a logical field group that this control belongs to.
All fields in a logical field group should share the same <code>fieldGroupId</code>. Once a logical field group is left, the <code>validateFieldGroup</code> event is raised.
See {@link sap.ui.core.Control#attachValidateFieldGroup}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="validateFieldGroup" type="xs:string">
<xs:annotation>
<xs:documentation>Event is fired if a logical field group defined by <code>fieldGroupIds</code> of a control was left or the user explicitly pressed a key combination that triggers validation.
Listen to this event to validate data of the controls belonging to a field group. See {@link sap.ui.core.Control#setFieldGroupIds}.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="CustomData" substitutionGroup="n0:Element" type="n0:_CustomDataType">
<xs:annotation>
<xs:documentation>Contains a single key/value pair of custom data attached to an Element. See method data().</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_CustomDataType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType">
<xs:attribute name="key" type="xs:string">
<xs:annotation>
<xs:documentation>The key of the data in this CustomData object. When the data is just stored, it can be any string, but when it is to be written to HTML (writeToDom == true) then it must also be a valid HTML attribute name (it must conform to the sap.ui.core.ID type and may contain no colon) to avoid collisions, it also may not start with "sap-ui". When written to HTML, the key is prefixed with "data-". If any restriction is violated, a warning will be logged and nothing will be written to the DOM.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="value" type="xs:string">
<xs:annotation>
<xs:documentation>The data stored in this CustomData object. When the data is just stored, it can be any JS type, but when it is to be written to HTML (writeToDom == true) then it must be a string. If this restriction is violated, a warning will be logged and nothing will be written to the DOM.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="writeToDom" type="xs:boolean">
<xs:annotation>
<xs:documentation>If set to "true" and the value is of type "string" and the key conforms to the documented restrictions, this custom data is written to the HTML root element of the control as a "data-*" attribute. If the key is "abc" and the value is "cde", the HTML will look as follows: &lt;SomeTag ... data-abc="cde" ... &gt; Thus the application can provide stable attributes by data binding which can be used for styling or identification purposes. ATTENTION: use carefully to not create huge attributes or a large number of them.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="Element" type="n0:_ElementType">
<xs:annotation>
<xs:documentation>Base Class for Elements.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ElementType">
<xs:sequence>
<xs:element minOccurs="0" name="tooltip">
<xs:annotation>
<xs:documentation>The tooltip that should be shown for this Element.
Can either be an instance of a TooltipBase subclass or a simple string.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0">
<xs:element ref="n0:TooltipBase" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="customData">
<xs:annotation>
<xs:documentation>Custom Data, a data structure like a map containing arbitrary key value pairs.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="n0:CustomData" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="layoutData">
<xs:annotation>
<xs:documentation>Defines the layout constraints for this control when it is used inside a Layout. LayoutData classes are typed classes and must match the embedding Layout. See VariantLayoutData for aggregating multiple alternative LayoutData instances to a single Element.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0">
<xs:element ref="n0:LayoutData" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="dependents">
<xs:annotation>
<xs:documentation>Dependents are not rendered, but their databinding context and lifecycle are bound to the aggregating Element.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="n0:Element" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="dragDropConfig">
<xs:annotation>
<xs:documentation>Defines the drag-and-drop configuration.
This aggregation is provided exclusively to test drag-and-drop functionality of all controls. It might be removed or the functionality might be limited due to control {@link sap.ui.core.Element.extend metadata} restrictions.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="n1:DragDropBase" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="id" type="n0:_IDType">
<xs:annotation>
<xs:documentation>The unique identifier within a page, either configured or automatically generated.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="class" type="xs:string">
<xs:annotation>
<xs:documentation>The CSS class to use with this element</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="tooltip" type="xs:string" />
<xs:attribute name="customData" type="xs:string" />
<xs:attribute name="dependents" type="xs:string" />
<xs:attribute name="dragDropConfig" type="xs:string" />
</xs:complexType>
<xs:element name="HTML" substitutionGroup="n0:Control" type="n0:_HTMLType">
<xs:annotation>
<xs:documentation>Embeds standard HTML in an SAPUI5 control tree.
Security Hint: By default, the HTML content (property 'content') is not sanitized and therefore open to XSS attacks. Applications that want to show user defined input in an HTML control, should either sanitize the content on their own or activate automatic sanitizing through the {@link #setSanitizeContent sanitizeContent} property.
Although this control inherits the <code>tooltip</code> aggregation/property and the <code>hasStyleClass</code>, <code>addStyleClass</code>, <code>removeStyleClass</code> and <code>toggleStyleClass</code> methods from its base class, it doesn't support them. Instead, the defined HTML content can contain a tooltip (title attribute) or custom CSS classes.
For further hints about usage restrictions for this control, see also the documentation of the <code>content</code> property.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_HTMLType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="content" type="xs:string">
<xs:annotation>
<xs:documentation>HTML content to be displayed, defined as a string.
The content is converted to DOM nodes with a call to <code>new jQuery(content)</code>, so any restrictions for the jQuery constructor apply to the content of the HTML control as well.
Some of these restrictions (there might be others!) are: <ul> <li>the content must be enclosed in tags, pure text is not supported. </li> <li>if the content contains script tags, they will be executed but they will not appear in the resulting DOM tree. When the contained code tries to find the corresponding script tag, it will fail.</li> </ul>
Please consider to consult the jQuery documentation as well.
The HTML control currently doesn't prevent the usage of multiple root nodes in its DOM content (e.g. <code>setContent("&lt;div/>&lt;div/>")</code>), but this is not a guaranteed feature. The accepted content might be restricted to single root nodes in future versions. To notify applications about this fact, a warning is written in the log when multiple root nodes are used.
When changing the content dynamically, ensure that the ID of the root node remains the same as the HTML control's ID. Otherwise it cannot be guaranteed that certain lifecycle events take place.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="preferDOM" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether existing DOM content is preferred over the given content string.
There are two scenarios where this flag is relevant (when set to true): <ul> <li>for the initial rendering: when an HTML control is added to a UIArea for the first time and if the root node of that UIArea contained DOM content with the same id as the HTML control, then that content will be used for rendering instead of any specified string content</li> <li>any follow-up rendering: when an HTML control is rendered for the second or any later time and the preferDOM flag is set, then the DOM from the first rendering is preserved and not replaced by the string content</li> </ul>
As preserving the existing DOM is the most common use case of the HTML control, the default value is true.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="sanitizeContent" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether to run the HTML sanitizer once the content (HTML markup) is applied or not.
To configure allowed URLs please use the whitelist API via jQuery.sap.addUrlWhitelist.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="afterRendering" type="xs:string">
<xs:annotation>
<xs:documentation>Fired after the HTML control has been rendered. Allows to manipulate the resulting DOM.
When the control doesn't have string content and no preserved DOM existed for this control, then this event will fire, but there won't be a DOM node for this control.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="Icon" substitutionGroup="n0:Control" type="n0:_IconType">
<xs:annotation>
<xs:documentation>Icon uses embedded font instead of pixel image. Comparing to image, Icon is easily scalable, color can be altered live and various effects can be added using css.
A set of built in Icons is available and they can be fetched by calling sap.ui.core.IconPool.getIconURI and set this value to the src property on the Icon.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_IconType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="src" type="n0:_URIType">
<xs:annotation>
<xs:documentation>This property should be set by the return value of calling sap.ui.core.IconPool.getIconURI with an Icon name parameter and an optional collection parameter which is required when using application extended Icons. A list of standard FontIcon is available here.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="size" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>Since Icon uses font, this property will be applied to the css font-size property on the rendered DOM element.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="color" type="xs:string">
<xs:annotation>
<xs:documentation>The color of the Icon. If color is not defined here, the Icon inherits the color from its DOM parent.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="hoverColor" type="xs:string">
<xs:annotation>
<xs:documentation>This color is shown when icon is hovered. This property has no visual effect when run on mobile device.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="activeColor" type="xs:string">
<xs:annotation>
<xs:documentation>This color is shown when icon is pressed/activated by the user.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="width" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>This is the width of the DOM element which contains the Icon. Setting this property doesn't affect the size of the font. If you want to make the font bigger, increase the size property.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="height" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>This is the height of the DOM element which contains the Icon. Setting this property doesn't affect the size of the font. If you want to make the font bigger, increase the size property.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="backgroundColor" type="xs:string">
<xs:annotation>
<xs:documentation>Background color of the Icon in normal state.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="hoverBackgroundColor" type="xs:string">
<xs:annotation>
<xs:documentation>Background color for Icon in hover state. This property has no visual effect when run on mobile device.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="activeBackgroundColor" type="xs:string">
<xs:annotation>
<xs:documentation>Background color for Icon in active state.
The property can be set with {@link sap.ui.core.CSSColor CSS Color} or {@link sap.ui.core.IconColor Semantic Icon Color}.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="decorative" type="xs:boolean">
<xs:annotation>
<xs:documentation>A decorative icon is included for design reasons. Accessibility tools will ignore decorative icons. Tab stop isn't affected by this property anymore and it's now controlled by the existence of press event handler and the noTabStop property.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="useIconTooltip" type="xs:boolean">
<xs:annotation>
<xs:documentation>Decides whether a default Icon tooltip should be used if no tooltip is set.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="alt" type="xs:string">
<xs:annotation>
<xs:documentation>This defines the alternative text which is used for outputting the aria-label attribute on the DOM.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="noTabStop" type="xs:boolean">
<xs:annotation>
<xs:documentation>Defines whether the tab stop of icon is controlled by the existence of press event handler. When it's set to false, Icon control has tab stop when press event handler is attached. If it's set to true, Icon control never has tab stop no matter whether press event handler exists or not.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="ariaLabelledBy" type="xs:string">
<xs:annotation>
<xs:documentation>Association to controls / ids which label this control (see WAI-ARIA attribute aria-labelledby).</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="press" type="xs:string">
<xs:annotation>
<xs:documentation>This event is fired when icon is pressed/activated by the user. When a handler is attached to this event, the Icon gets tab stop. If you want to disable this behavior, set the noTabStop property to true.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="InvisibleText" substitutionGroup="n0:Control" type="n0:_InvisibleTextType">
<xs:annotation>
<xs:documentation>An InvisibleText is used to bring hidden texts to the UI for screen reader support. The hidden text can e.g. be referenced in the ariaLabelledBy or ariaDescribedBy associations of other controls.
The inherited properties busy, busyIndicatorDelay and visible and the aggregation tooltip is not supported by this control.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_InvisibleTextType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="text" type="xs:string">
<xs:annotation>
<xs:documentation>The text of the InvisibleText.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="Item" substitutionGroup="n0:Element" type="n0:_ItemType">
<xs:annotation>
<xs:documentation>A control base type.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ItemType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType">
<xs:attribute name="text" type="xs:string">
<xs:annotation>
<xs:documentation>The text to be displayed for the item.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="enabled" type="xs:boolean">
<xs:annotation>
<xs:documentation>Enabled items can be selected.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="textDirection" type="n0:_TextDirectionType">
<xs:annotation>
<xs:documentation>Options are RTL and LTR. Alternatively, an item can inherit its text direction from its parent control.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="key" type="xs:string">
<xs:annotation>
<xs:documentation>Can be used as input for subsequent actions.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="LayoutData" substitutionGroup="n0:Element" type="n0:_LayoutDataType">
<xs:annotation>
<xs:documentation>A layout data base type.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_LayoutDataType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType" />
</xs:complexContent>
</xs:complexType>
<xs:element name="ListItem" substitutionGroup="n0:Item" type="n0:_ListItemType">
<xs:annotation>
<xs:documentation>An item that is used in lists or list-similar controls such as DropdownBox, for example. The element foresees the usage of additional texts displayed in a second column.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ListItemType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ItemType">
<xs:attribute name="icon" type="xs:string">
<xs:annotation>
<xs:documentation>The icon belonging to this list item instance. This can be a URI to an image or an icon font URI.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="additionalText" type="xs:string">
<xs:annotation>
<xs:documentation>Some additional text of type string, optionally to be displayed along with this item.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="LocalBusyIndicator" substitutionGroup="n0:Control" type="n0:_LocalBusyIndicatorType">
<xs:annotation>
<xs:documentation>The LocalBusyIndicator is a special version of the BusyIndicator. This one doesn't block the whole screen - it just blocks the corresponding control and puts a local animation over the control. To use the functionality of this control the corresponding control needs to be enabled via the 'LocalBusyIndicatorSupport' accordingly to the ListBox control (see the init-function of the ListBox).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_LocalBusyIndicatorType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="width" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>This property is the width of the control that has to be covered. With this width the position of the animation can be properly set.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="height" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>This property is the height of the control that has to be covered. With this height the position of the animation can be properly set.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="Message" substitutionGroup="n0:Element" type="n0:_MessageType">
<xs:annotation>
<xs:documentation>This element used to provide messages. Rendering must be done within the control that uses this kind of element.
Its default level is none.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_MessageType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType">
<xs:attribute name="text" type="xs:string">
<xs:annotation>
<xs:documentation>Message text</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="timestamp" type="xs:string">
<xs:annotation>
<xs:documentation>Message's timestamp. It is just a simple String that will be used without any transformation. So the application that uses messages needs to format the timestamp to its own needs.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="icon" type="n0:_URIType">
<xs:annotation>
<xs:documentation>A possible icon URI of the message</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="level" type="n0:_MessageTypeType">
<xs:annotation>
<xs:documentation>Setting the message's level.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="readOnly" type="xs:boolean">
<xs:annotation>
<xs:documentation>Determines whether the message should be read only. This helps the application to handle a message a different way if the application differentiates between read-only and common messages.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="ScrollBar" substitutionGroup="n0:Control" type="n0:_ScrollBarType">
<xs:annotation>
<xs:documentation>The ScrollBar control can be used for virtual scrolling of a certain area. This means: to simulate a very large scrollable area when technically the area is small and the control takes care of displaying the respective part only. E.g. a Table control can take care of only rendering the currently visible rows and use this ScrollBar control to make the user think he actually scrolls through a long list.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_ScrollBarType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="vertical" type="xs:boolean">
<xs:annotation>
<xs:documentation>Orientation. Defines if the Scrollbar is vertical or horizontal.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="scrollPosition" type="xs:int">
<xs:annotation>
<xs:documentation>Scroll position in steps or pixels.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="size" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>Size of the Scrollbar (in pixels).</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="contentSize" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>Size of the scrollable content (in pixels).</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="steps" type="xs:int">
<xs:annotation>
<xs:documentation>Number of steps to scroll. Used if the size of the content is not known as the data is loaded dynamically.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="scroll" type="xs:string">
<xs:annotation>
<xs:documentation>Scroll event.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="SeparatorItem" substitutionGroup="n0:Item" type="n0:_SeparatorItemType">
<xs:annotation>
<xs:documentation>An item that provides a visual separation. It borrows all its methods from the classes sap.ui.core.Item, sap.ui.core.Element, sap.ui.base.EventProvider, and sap.ui.base.Object.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_SeparatorItemType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ItemType" />
</xs:complexContent>
</xs:complexType>
<xs:element name="Title" substitutionGroup="n0:Element" type="n0:_TitleType">
<xs:annotation>
<xs:documentation>Represents a title element that can be used for aggregation with other controls</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_TitleType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ElementType">
<xs:attribute name="text" type="xs:string">
<xs:annotation>
<xs:documentation>Defines the title text</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="icon" type="n0:_URIType">
<xs:annotation>
<xs:documentation>Defines the URL for icon display</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="level" type="n0:_TitleLevelType">
<xs:annotation>
<xs:documentation>Defines the level of the title. If set to auto the level of the title is chosen by the control rendering the title.
Currently not all controls using the Title.control supporting this property.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="emphasized" type="xs:boolean">
<xs:annotation>
<xs:documentation>If set the title is displayed emphasized. This feature is nor supported by all controls using the Title.control.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="TooltipBase" substitutionGroup="n0:Control" type="n0:_TooltipBaseType">
<xs:annotation>
<xs:documentation>Abstract class that can be extended in order to implement any extended tooltip. For example, RichTooltip Control is based on it. It provides the opening/closing behavior and the main "text" property.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_TooltipBaseType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="text" type="xs:string">
<xs:annotation>
<xs:documentation>The text that is shown in the tooltip that extends the TooltipBase class, for example in RichTooltip.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="openDuration" type="xs:int">
<xs:annotation>
<xs:documentation>Optional. Open Duration in milliseconds.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="closeDuration" type="xs:int">
<xs:annotation>
<xs:documentation>Optional. Close Duration in milliseconds.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="myPosition" type="n0:_DockType">
<xs:annotation>
<xs:documentation>Optional. My position defines which position on the extended tooltip being positioned to align with the target control.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="atPosition" type="n0:_DockType">
<xs:annotation>
<xs:documentation>Optional. At position defines which position on the target control to align the positioned tooltip.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="offset" type="xs:string">
<xs:annotation>
<xs:documentation>Optional. Offset adds these left-top values to the calculated position. Example: "10 3".</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="collision" type="n0:_CollisionType">
<xs:annotation>
<xs:documentation>Optional. Collision - when the positioned element overflows the window in some direction, move it to an alternative position.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="openDelay" type="xs:int">
<xs:annotation>
<xs:documentation>Opening delay of the tooltip in milliseconds</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="closeDelay" type="xs:int">
<xs:annotation>
<xs:documentation>Closing delay of the tooltip in milliseconds</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="closed" type="xs:string">
<xs:annotation>
<xs:documentation>This event is fired when the Tooltip has been closed</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="VariantLayoutData" substitutionGroup="n0:LayoutData" type="n0:_VariantLayoutDataType">
<xs:annotation>
<xs:documentation>Allows to add multiple LayoutData to one control in case that an easy switch of layouts (e.g. in a Form) is needed.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_VariantLayoutDataType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_LayoutDataType">
<xs:sequence>
<xs:element minOccurs="0" name="multipleLayoutData">
<xs:annotation>
<xs:documentation>Allows multiple LayoutData.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="n0:LayoutData" />
<xs:element ref="n0:Fragment" />
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="multipleLayoutData" type="xs:string" />
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="XMLComposite" substitutionGroup="n0:Control" type="n0:_XMLCompositeType">
<xs:annotation>
<xs:documentation>Base Class for XMLComposite controls.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="_XMLCompositeType">
<xs:complexContent mixed="false">
<xs:extension base="n0:_ControlType">
<xs:attribute name="width" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>The width</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="height" type="n0:_CSSSizeType">
<xs:annotation>
<xs:documentation>The height</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="displayBlock" type="xs:boolean">
<xs:annotation>
<xs:documentation>Whether the CSS display should be set to "block".</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:simpleType name="_AbsoluteCSSSizeType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_CollisionType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_CSSColorType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_CSSSizeType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_CSSSizeShortHandType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_DockType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_IDType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_PercentageType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_URIType">
<xs:restriction base="xs:string" />
</xs:simpleType>
<xs:simpleType name="_AccessibleLandmarkRoleType">
<xs:restriction base="xs:string">
<xs:enumeration value="Banner">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>banner</code>.
A banner usually appears at the top of the page and typically spans the full width.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Complementary">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>complementary</code>.
A section of the page, designed to be complementary to the main content at a similar level in the DOM hierarchy.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Main">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>main</code>.
The main content of a page.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Navigation">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>navigation</code>.
A region that contains a collection of items and objects that, as a whole, combine to create a navigation facility.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="None">
<xs:annotation>
<xs:documentation>No explicit role is applicable.
The interpretation of this value depends on the control / element which defines a property with this type. Normally this value means that no accessible landmark should be written.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Region">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>region</code>.
A section of a page, that is important enough to be included in a page summary or table of contents.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Search">
<xs:annotation>
<xs:documentation>Represents the ARIA role <code>search</code>.
A region that contains a collection of items and objects that, as a whole, combine to create a search facility.</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="_AccessibleRoleType">
<xs:restriction base="xs:string">
<xs:enumeration value="Alert">
<xs:annotation>
<xs:documentation>A message with an alert or error information.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AlertDialog">
<xs:annotation>
<xs:documentation>A separate window with an alert or error information.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Application">
<xs:annotation>
<xs:documentation>A software unit executing a set of tasks for the user.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Banner">
<xs:annotation>
<xs:documentation>Usually defined as the advertisement at the top of a web page. The banner content typically contains the site or company logo, or other key advertisements.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Button">
<xs:annotation>
<xs:documentation>Allows user-triggered actions.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Checkbox">
<xs:annotation>
<xs:documentation>A control that has three possible values: true, false, mixed.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ColumnHeader">
<xs:annotation>
<xs:documentation>A table cell containing header information for a column.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Combobox">
<xs:annotation>
<xs:documentation>Allows selecting an item from a list, or to enter data directly in the input field.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ContentInfo">
<xs:annotation>
<xs:documentation>Information about the content on the page. Examples are footnotes, copyrights, or links to privacy statements.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Definition">
<xs:annotation>
<xs:documentation>The content of the associated element represents a definition. If there is a definition element within the content, this one represents the term being defined.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Description">
<xs:annotation>
<xs:documentation>Descriptive content for a page element.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Dialog">
<xs:annotation>
<xs:documentation>A small window that is designed to interrupt the current application processing in order to inform the user and to get some response.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Directory">
<xs:annotation>
<xs:documentation>A list of references to members of a single group.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Document">
<xs:annotation>
<xs:documentation>Content that contains related information, such as a book.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Grid">
<xs:annotation>
<xs:documentation>Contains cells of tabular data arranged in rows and columns, for example in a table.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GridCell">
<xs:annotation>
<xs:documentation>A table cell in a grid where the cells can be active, editable, and selectable. Cells may have functional relationships to controls, for example.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Group">
<xs:annotation>
<xs:documentation>A section of user interface objects.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Heading">
<xs:annotation>
<xs:documentation>A heading for a section of the page.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Img">
<xs:annotation>
<xs:documentation>A container for a collection of elements that form an image.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Link">
<xs:annotation>
<xs:documentation>An interactive reference to a resource.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="List">
<xs:annotation>
<xs:documentation>A container for non-interactive list items which are the children of the list.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Listbox">
<xs:annotation>
<xs:documentation>A widget that allows the user to select one or more items from a list. The items within the list are static and can contain images.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ListItem">
<xs:annotation>
<xs:documentation>A single item in a list.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Log">
<xs:annotation>
<xs:documentation>An area where new information is added, or old information disappears. Information types are chat logs, messaging, or error logs, for example. The log contains a sequence: New information is always added to the end of the log.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Main">
<xs:annotation>
<xs:documentation>Defines the main content of a document.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Marquee">
<xs:annotation>
<xs:documentation>Is used to scroll text across the page.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Menu">