IFrame 

We can recommend only with reservations the use of the IFrame UI element. An IFrame is an area of the browser window in which stateless contents (images and documents) are displayed using a separate source URI. This source is displayed in the IFrame and handled by the browser exactly like a stateless document. This has the following consequences:

When interactive stateful applications (for example, BSP and JSP applications) are embedded, they remain in their current state once the user leaves the whole page. When the page is called up again (for example, the user navigates back to it), the content of the IFrame is completely rebuilt. In particular, this means that the stateful application is restarted. As a result the context, for example, of the embedded application, exists twice in the backend, because session-wide handling of Web Dynpro ABAP is not supported with use of the IFrame. Furthermore, the Web Dynpro Framework cannot close existing (multiple) sessions that were started through the use of IFrames.

It is important to know that the embedding of Web Dynpro applications in IFrames is not supported.

The OfficeControl is provided for embedding documents and the InteractiveForm is provided for PDF forms. You can use certain UI elements to embed help texts, for example, Explanation and the explanation property in a range of UI elements (for example, InputField, Button).

Keep in mind that accessibility of the IFrame content is not provided by Web Dynpro. This means that the project in whose area of responsibility the IFrame is used is responsible for the accessibility of the content displayed in the IFrame. The same applies to Right-to-Left (RTL) support.

The IFrame may not be used in a ScrollContainer with scrollingMode not equal to none.  The ScrollContainer is obsolete.

 

IFrames must not be used in scrolling containers, such as Groups, Trays, TransparentContainers with scrollbars, and Popups.

 

Example of the Visual Display:
IFrame in a MatrixLayout with Background Shading

To enable the development of accessible applications, the tooltip property is checked during the syntax check.

 

Runtime Class

CL_WD_IFRAME

 

Properties in the View Designer

Name	Type	Initial Value	Bindable
id	STRING	(automatic)	No
border	WDY_BOOLEAN	false	Yes
contextMenuBehaviour	WDUI_CONTEXT_MENU_BEHAVIOUR	inherit	No
contextMenuId	WDY_MD_UI_ELEMENT_REFERENCE		No
enabled	WDY_BOOLEAN	true	Yes
height	STRING	300	Yes
scrollingMode	WDUI_SCROLLING_MODE	auto	Yes
source	STRING		Yes
tooltip	Translatable text		Yes
visible	WDUI_VISIBILITY	visible	Yes
width	STRING	300	Yes

Other properties that can be inherited are defined in the associated higher-level classes. The associated UI elements are:

 

·         UIElement

·         ContextMenuProvider

·         ViewElement

Dynamic Programming

For dynamic programming, the same properties, events, and aggregations as in the View Designer are available. Bear in mind the different spellings.

Dynamic Programming of Properties

View Designer Name	Runtime Name	Type
border	BORDER	WDY_BOOLEAN
contextMenuBehaviour	CONTEXT_MENU_BEHAVIOUR	WDUI_CONTEXT_MENU_BEHAVIOUR
contextMenuBehaviour: inherit	CL_WD_IFRAME=>E_CONTEXT_MENU_BEHAVIOUR-INHERIT
contextMenuBehaviour: provide	CL_WD_IFRAME=>E_CONTEXT_MENU_BEHAVIOUR-PROVIDE
contextMenuBehaviour: suppress	CL_WD_IFRAME=>E_CONTEXT_MENU_BEHAVIOUR-SUPPRESS
contextMenuId	CONTEXT_MENU_ID	WDY_MD_UI_ELEMENT_REFERENCE
enabled	ENABLED	WDY_BOOLEAN
height	HEIGHT	STRING
scrollingMode	SCROLLING_MODE	WDUI_SCROLLING_MODE
scrollingMode: auto	CL_WD_IFRAME=>E_SCROLLING_MODE-AUTO
scrollingMode: both	CL_WD_IFRAME=>E_SCROLLING_MODE-BOTH
scrollingMode: none	CL_WD_IFRAME=>E_SCROLLING_MODE-NONE
source	SOURCE	STRING
tooltip	TOOLTIP	WDY_MD_TRANSLATABLE_TEXT
visible	VISIBLE	WDUI_VISIBILITY
visible: none	CL_WD_IFRAME=>E_VISIBLE-NONE
visible: visible	CL_WD_IFRAME=>E_VISIBLE-VISIBLE
width	WIDTH	STRING

 

Example

You can find examples in the system in the Web Dynpro application, WDR_TEST_UI_ELEMENTS.