
Properties in View Designer
accessibilityDescription
If you have activated accessibility, the assigned text is added to the quick info. This description provides semantic details of the UI element, and is only read by the screen reader if the user focuses the complete Ul element.
This property can be personalized by administrators.
ariaLandmark
With this property you can define Accessible Rich Internet Applications (ARIA) landmarks for container UI elements Group, Tray, Panel, PanelStack, ScrollContainer, and TransparentContainer. You select the UI element function to enable users to navigate with a screen reader within your application. If you set the ariaLandmark property, ARIA landmarks are added to an HTML element by the role attribute.
|
Value |
Description |
|---|---|
|
Application |
Web application area (in contrast to web document) |
|
Article |
Area consisting of an independent part of a document or a page (e.g. forum post, magazine article, web log entry, user comment) |
|
Banner |
Page header |
|
Complementary |
Area with supplementary information that supports the main content and is comprehensible without reference to this information |
|
Contentinfo |
Metadata that relates to the parent document (e.g. footnotes, copyright, or links to data protection statements) |
|
Form |
Elements that together make up a form. |
|
Main |
Main content area |
|
Navigation |
Elements to navigate within the document or to similar documents (e.g. links). |
|
None |
No landmark role |
|
Search |
Area with search function |
defaultButtonId
ID of the assigned default button.
Note that the button defined as the defaultButton for the RootContainer must be a child element of the container for which it is entered as the defaultButton. More information: TransparentContainer Properties.
This property can be personalized by administrators.
handleHotkeys
Specifies whether hot keys defined within the UI element can be triggered globally or locally (when the focus is in the UI element).
scrollingMode
Display of the scroll bar within the UI element.
Note that active elements are not supported in scrollable elements. This means that the Network, Gantt, OfficeControl, and InteractiveForm UI elements cannot be used in a container with scrollingMode <> none. If they are used, these elements are positioned incorrectly on the page.
This property can be personalized by administrators.
Value |
Description |
Can be Set Using Personalization |
|---|---|---|
auto |
The scroll bar within the container is activated automatically. Note that ta value must be set with property height. |
Yes |
both |
A vertical and horizontal scroll bar are activated. |
Yes |
none |
If necessary, the container is made larger so that the entire content can be displayed without scrolling. |
Yes |
scrollLeft
Horizontal position of the scrollbar
scrollLeft can only be set or read dynamically. It is not possible to bind scrollLeft to the context.
scrollTop
Vertical position of the scrollbar
scrollTop can only be set or read dynamically. It is not possible to bind scrollTop to the context.
The following getter and setter methods are available to get or set the vertical and horizontal position of the scrollbar:
GET_SCROLL_LEFT: Gets the horizontal scroll position
GET_SCROLL_TOP: Gets the vertical scroll position
SET_SCROLL_LEFT: Sets the horizontal scroll position
SET_SCROLL_TOP: Sets the vertical scroll position
The initial value of the attributes scrollLeft and scrollTop is -1. You can no longer reach this value by scrolling. This allows the application to determine whether the container has been scrolled or not. Therefore, the smallest value that can be reached after scrolling in either direction is 0.