|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
UI Automation Support for the Table Control Type
This topic provides information about UI Automation support for the Table control type. In UI Automation, a control type is a set of conditions that a control must meet in order to use the ControlTypeProperty property. The conditions include specific guidelines for UI Automation tree structure, UI Automation property values and control patterns.
Table controls contain rows and columns of text, and optionally, row headers and column headers.
The following sections define the required UI Automation tree structure, properties, control patterns, and events for the Table control type. The UI Automation requirements apply to all table controls, whether Windows Presentation Foundation (WPF), Win32, or Windows Forms.
This topic contains the following sections.
The following table depicts the control view and the content view of the UI Automation tree that pertains to table controls and describes what can be contained in each view. For more information on the UI Automation tree, see UI Automation Tree Overview.
If a table control has row or column headers, they must be exposed in the Control View of the UI Automation tree. The Content View does not need to expose this information because it can be accessed using the TablePattern.
Note that there is always at least one text element in the subtree of the Table element.
The following table lists the UI Automation properties whose value or definition is especially relevant to Table controls. For more information about UI Automation properties, see UI Automation Properties for Clients.
UI Automation Property
The value of this property needs to be unique across all controls in an application.
The outermost rectangle that contains the whole control.
Supported if there is a bounding rectangle. If not every point within the bounding rectangle is clickable, and you perform specialized hit testing, then override and provide a clickable point.
If the control can receive keyboard focus, it must support this property.
The table control typically gets its name from a static text label. If there is no static text label, you must assign a Name property that must always be available to explain the purpose of the table.
If there is a static text label, then this property must expose a reference to that control.
This value is the same for all UI frameworks.
Localized string corresponding to the Table control type.
More details about the purpose of the table should be exposed through this property if it is not sufficiently explained by accessing the NameProperty.
The table control must always be content.
The table control must always be a control.
The following table lists the UI Automation control patterns required to be supported by Table controls. For more information on control patterns, see UI Automation Control Patterns Overview.
Control Pattern/Pattern Property
The table control always supports this control pattern because the items that it contains have data that is presented in a grid.
The table control always has the capability of having headers associated with the content.
If the text element is contained within a table control, this must be supported.
The following table lists the UI Automation events required to be supported by all table controls. For more information on events, see UI Automation Events Overview.