UI Control Rendering in Standards Mode
Since the way a UI control is rendered is dependent on browser mode and platform, you may have to adjust your applications accordingly.
Standards mode is required if you want to run Web Dynpro ABAP or Floorplan Manager (FPM) applications embedding HTML5 UI elements (for example, Web Dynpro ABAP's HTMLIsland and Chart controls, or FPM's Visual Business GUIBB).
Most browsers are able to switch your applications to run in Standards mode (for example, Firefox, Safari, Google Chrome, and Microsoft Internet Explorer 9 and higher). However, this is not possible with Internet Explorer 8 and lower versions, with the result that your application might look or behave differently from what you expect.
As of version 9, Internet Explorer replaces Quirks mode with a new mode, the Quirks Mode Emulation (QME). It is based on the new standards mode rendering engine. Applications designed to run in Quirks mode, may look different in this new mode. However, Web Dynpro ABAP does not support QME for IE9.
Additionally, you cannot combine different IE render engines on a browser page. For example, the IE9 Standards mode cannot be combined on a page with the IE8 Quirks mode. For each frame, a selection can be made from the available modes of the rendering engine set. Hence, if the shell (for example, SAP NetWeaver Business Client (NWBC) or SAP Enterprise Portal) requires Standards mode, the embedded application must also run in Standards mode.
The browser versions and platforms supported by Web Dynpro ABAP are published in the Platform
Availability Matrix (see SAP Service Marketplace
).
For more information on the supported browser modes, see
1753544 .
For more information on different IE rendering engines, see here
.
You can use the application parameter WDPREFERREDRENDERING to specify the desired rendering mode for Web Dynpro ABAP applications and application configurations.
For more information, see Application Parameters and URL Parameters.
You cannot combine different IE render engines on a browser page (for example, IE9 Standards mode with IE8 Quirks mode). Several solutions are available to this problem.
Defining the rendering mode using URL parameter
If a Web Dynpro ABAP application is embedded in an iFrame, the embedded page requires the same mode as the shell.Since the information on the mode of the shell is not available to a Web Dynpro ABAP application in the backend, you use URL parameter sap-ie to specify the preferred rendering mode.
For more information, see SAP URL Parameters.
SAP Note 1814711
describes how
you can configure the parameter in the portal.-
Automatically switching the rendering mode
- SAP NetWeaver Business Client (NWBC) for HTML
If NWBC is running on the same server instance as the Web Dynpro ABAP application, it is possible for NWBC to retrieve the preferred render mode before starting the application. In this case, NWBC adjusts its own rendering to the rendering of the embedded application. To achieve this, method CL_WDR_PORTAL_INTEGRATION=>GET_PREFERRED_RENDERING_MODE is used.
For more information, see SAP Note 1956448
. - Web Dynpro ABAP in IFrame
If the Web Dynpro ABAP application is started with a render mode different from the embedding shell, the Web Dynpro framework tries to restart the application with another render mode. This means, if the application was first started in Standards mode, the framework tries to switch to Quirks mode and vice versa. A restart in another rendering mode will not take place if the render mode is defined with URL parameter sap-wd-htmlrendermode.
The restart is visible to the user because a popup appears telling the user that the rendering is not valid. This popup disappears after a short time and the application is restarted in the other render mode. The restart can be avoided by setting the correct render mode using parameter sap-ie.
If the application is restarted with Quirks because the embedding shell has pretended this but the application can only run with Standards (parameter is set to value STAND_ONLY for the application), the application is restarted but stops with an error message.
For more information, see SAP Note 1996956
.
- SAP NetWeaver Business Client (NWBC) for HTML
- Standards mode applications in the SAP Enterprise Portal
Since Classic Framework Pages do not support standards mode, you must start an application that requires standards mode in a separate window.
For more information, see SAP Note 1737445
.
You may want to check at server-side in which render mode your application is run. You can use method GET_HTML_RENDER_MODE( ) of interface IF_WD_APPLICATION to retrieve this information. If the scenario does not support the required mode, you can implement how your application should react (for example, by navigating to an error page).
In addition, browsers provide tools to check on client-side in which mode the application is run. For example, if you run your application in Internet Explorer, you can press F12 to open the IE Developer Toolbar, which displays the document mode.
- The FPM configuration editor, FLUID, checks the static configuration of an application to see whether it contains HTML5 elements. If it detects the presence of these, the editor displays a message to warn that these elements must be run in Standards mode.
- You can use all FPM standard GUIBBs and floorplans with the HTML standards mode without adjustments unless restrictions are documented.
- Applications can run in the HTML standards mode if they consist only of FPM standard GUIBBs and floorplans, or were released by the respective application group for use.