Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 2812

FPM in standards mode in EP

$
0
0

Hello,

 

We are experiencing problems when trying to start a FPM application in standards mode in the enterprise portal. (7.40 SP11)

 

Error:

The FPM we are trying to start contains HTML islands. Currently when we try to start the view with the HTML islands we are getting shortdump: 'To use a UI element of type HTML_ISLAND, the application must be executed in the "Standards" browser mode'. However our portal runs in standards mode and at the moment we don't see why this application isn't handled as such.

 

Flow:

- FPM application is started in our portal. When starting the portal, the HTTP response header x-ua-compatible with value IE=edge is visible in Fiddler. IE Developer tools indicates 'Standards' mode is the default rendering mode.

- When clicking on a specific button inside this FPM, another FPM is opened in a new browser window. This application is also embedded in the portal and is started via a Quick Link.

- The new window is started and again the HTTP header x-ua-compatible: IE=edge is visible in Fiddler. However when navigating to the view with the HTML island, the short dump occurs.

 

After consulting lots of documentation, we changed the configuration on diverse levels but for now without success:

- FPM application parameter WDPREFERREDRENDERING to "standards"

- iView config:

     - Hand over Browser Document Mode Parameter: checked

     - added application parameter: sap-ie=EDGE

     - Default Document Rendering Mode: Standards

     - Launch in nwe Window: Display in separate headerless portal window (standards mode) (although I don't think this will affect the behaviour since it's started via a Quick Link?)

 

I guess we overlook something... Please let me know if something is not clear!

 

Any help is greatly appreciated!

Kind regards,

Maarten


Viewing all articles
Browse latest Browse all 2812

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>