Java WD drop-downs not working correctly

[Former Member]

Hi all:

My company is upgrading from NW 7.0 2004s to NW 7.4 SP14. We've just recently gotten over a big challenge getting applications running GUI for HTML trans-iViews & Java WD applications requiring Classic Event Framework to live on the same portal server by using the following settings:

- Under Portal Content > Portal Users > Standard Portal Users > Classic Framework Page > Browser Document Mode, the Browser Document Mode setting is now “IE=EDGE”.

- Under each SAPGUI Report’s trans-iView, the ‘Default Document Rendering Mode’ is set to ‘Standard’.

We've done this because my company requires us to standardize on Internet Explorer 11, both on Windows 7 & Windows 10. Unfortunately, this has caused a number of serious Java WD UI issues (pictures attached), such as:

- drop-down boxes are now only 1-3 rows visible when selected, no matter how many values they contain, making it difficult to select, see and scroll between all possible values.

- input text boxes now overlap their description labels instead of being painted adjacent to them.

- within tables, 1st row dropdown values are the only ones ever displayed, even when selecting another row’s dropdown values, including when that lower row is the lead selection.

After reading https://wiki.scn.sap.com/wiki/display/JSTSG/(IFWDJ)Problem-0232, I thought the sap.valuesetlimit.maxondemand property would fix this, then realized that this doesn't control the default visibility of how many can be seen at once.

In Studio 7.0 you can can control the Size property of drop-downs by switching between Small & Standard, but after migrating all our Java WD code to NW 7.4, this value has been deprecated and is no longer under our control.

I'm out of ideas. Nothing like these ever happened in NW 7.0 portal servers. Have any of you experienced these or similar issues? Any suggestions for what we can do to fix them?

Please advise,

Jon

[kiruthika_s]

Hi,

If you are using browser document mode in edge then all the application use standard

Refer below note:

1458799 - Limited supportability for IE8 and above in the Portal

1814711 - SAP applications iViews in EP: Rendering Modes

Regards

Kiruthika

[Former Member]

Hi Kiruthika:

As I tried to explain earlier we cannot use Browser Document Mode property value to IE=5, IE=EmulateIE7, because GUI for HTML trans-iViews that are also part of this same application will render incorrectly, specifically that F4 help and all inbox boxes are frozen and cannot be typed in, edited or changed.

We have standardized on IE11, but GUI for HTML trans-iViews & Java WD applications requiring Classic Event Framework must live on the same portal server.

Thanks,

Jon