Introduction

From Internet Explorer 8 onwards, Microsoft gradually shifted its strategy, moving from the old quirks mode concept towards full standards mode rendering. The limitation of this strategy is that you cannot run quirks mode content on the same page as standards mode content. The only way to do so is to render it in a new window.

This change of approach has caused many issues in SAP Enterprise Portal (and in any other Web applications that were implemented in the quirks mode environment). These issues and the ways to solve them are described in the following SCN blog http://scn.sap.com/community/enterprise-portal/blog/2014/09/03/ie-and-portal-standardsquirks-mode-evolution-or-love-hate-relationships).

Since the strategy of all Web applications is to move towards the standards mode rendering approach, SAP Enterprise Portal implemented new framework pages that fully support standards mode rendering: the Ajax Standard Mode framework page and the Fiori Framework page (FFP). For more information about these framework pages, see SAP Note # 2001910 (Ajax Framework Page standards) and SAP Note #2031108 (FFP). For FFP, you can also refer to the following blog SAP Fiori Launchpad in SAP Enterprise Portal: Overview Information.

The purpose of this document is to provide guidelines for content transitions from a quirks mode environment to a standards mode environment.

Terminology:

Quirks framework page – a framework page that specifies that the browser renders in quirks mode (IE5 quirks in IE10 and higher). For example, Classic Framework Page, Light Framework Page, Ajax Framework Page or any custom framework page based on the afore mentioned framework pages.

Standards framework page – a framework page that specifies that the browser render in standards mode (edge). For example, Ajax Standard Mode Framework Page, Fiori Framework page, or any custom framework page based on the Ajax Standard Mode Framework Page.


How Do I Set Up a Framework Page to Run in Either Quirks or Standards Mode?

To force browsers to render in your chosen mode, insert an out-of-the-box Browser Document Mode iView into the framework page and set the Browser Document Mode property of the iView to be “IE=5, IE=EmulateIE7” for quirks mode or “IE=edge” for standards mode (for more information, see SAP Note #1458799).

Standards mode support

UI Technology

Portal Versions

SAP Note

WD ABAP

7.02 SP15, 7.30 SP11, 7.31 SP5, 7.40

1753544

WD Java

7.30 SP 9, 7.31 SP1, 7.40

1854758

SAP GUI for HTML

7.00, 7.01, 7.30, 7.31, 7.40

1924378

BSP

Not supported

In process

BW

Not supported

In process








Content migration steps


A quirks framework page can contain three types of content:

  • Quirks mode rendering applications
  • Standards mode rendering applications (Launch in New Window property of the iView is set to “Display in separate headerless portal window (standards mode)”).
  • Standalone running applications.

Steps needed for Quirks mode rendering applications


If the application has been implemented in an SAP UI technology which supports dual rendering and your portal version is one of the versions mentioned in SAP Note #1814711 then you don’t have to do anything! (Dual rendering means that the application supports both quirks and standards mode rendering. In the “Standards mode support” table above, you can see which technology supports standards mode, and in which versions.)

The portal notifies the backend of the standards mode environment and the application renders in the correct mode.

If the application is based on an SAP UI technology, which does not yet support standards mode, or if you cannot upgrade your backend, then you must set the iView\Page property Launch in New Window to Display in separate headerless portal window. This mode will force the browser to open a new window rendered in quirks mode.

Diagram.JPG

Steps needed for standards mode rendering applications


If the application is rendered in a quirks mode rendering framework page, you have to set the property “Launch in New Window” of these iViews to “Display in separate headerless portal window (standards mode)” than no further action is necessary. The application will continue to function as before.

If you want the application to render in-place, then you can change the property “Launch in New Window” of the iView to “Display in Portal Content Area”.

Steps needed for Standalone rendering applications


When we talk about standalone rendering applications, we mean that the iViews are launched directly in a separate browser window.

By directly, we mean that it is done without using the portal navigation API.

One example of direct launch is the following URL:

“<protocol>://<server>:<port>/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct…”

Another example is when executing the iView in “preview” mode (through iView\Page editor).

In SAP Notes 2098706, 2097861, and 2012705, we explained a new iView/page property, “Default Document Rendering Mode”. You can set the value to either “Quirks” or “Standards” to force the required rendering mode in standalone scenarios.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Dayong Sun

    I have a BSP application that uses HTML/AngularJS. It does not use HTMLB stuff. Can I make it run in standard mode? We use EP 7.4.

    (0) 

Leave a Reply